No plugin found for prefix 'releaser' about multi-module-maven-release-plugin

[danielflower]

I did a bit more digging around this. This will happen in a multi-module project where there is at least one module that does not have a parent in the same repo (or more specifically, when a module and its parent don't declare the release plugin).

I hope to spend some time to see if I can get around this. Until then, use the fully qualified name or declare the plugin in any module that doesn't inherit the plugin from an ancestor pom already.

Edit: somehow I missed the excellent explanation above from @frizzlebit when writing this comment. That is exactly the problem.

[bbolli]

The solution that worked for me without changing any POMs was to add this to my .m2/settings.xml:

<pluginGroups>
  <pluginGroup>com.github.danielflower.mavenplugins</pluginGroup>
</pluginGroups>

[danielflower]

Hi Darren, yes I think this should be simple....

You need to move the plugin declaration outside of the pluginManagement node. The <plugins> node should be a direct descendent of the <build> node. Give that a try and let me know how it goes.

Cheers.

[pmibal]

I am experiencing the exact same issue. @darrin, did the solution work for you?

[danielflower]

I actually saw this on one project where everything appeared to be set up correctly. Maven was ignoring the prefix for some reason. Can you try multi-module-maven-release-plugin:release instead? Or maybe com.github.danielflower.mavenplugins:multi-module-maven-release-plugin:release

[darrin]

Sorry guys - I'm a victim of shifting priorities and got pulled off that project shortly after reporting the issue.

[frizzlebit]

I found that the missing prefix error is a generic maven issue related to how you declare the plugin.

I found that I needed to declare the plugin within /build/pluginManagement/plugins of the multi-module pom.xml you use to start the build. You must also declare it in the same section of all the children modules.

This is probably because I use a project structure where inheritance information is kept in a parent pom.xml that is separate from an 'aggregator pom' used to list all the modules for build/release. There is no relationship between the 'aggregator pom' and the parent pom.

My example:

    <build>
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>com.github.danielflower.mavenplugins</groupId>
                    <artifactId>multi-module-maven-release-plugin</artifactId>
                    <version>1.0.2</version>
                </plugin>           
            </plugins>
        </pluginManagement>
        <plugins>
            <!-- 
            | Get more detail with: mvn releaser:help -Ddetail=true -Dgoal=release 
            -->
            <plugin>
                <groupId>com.github.danielflower.mavenplugins</groupId>
                <artifactId>multi-module-maven-release-plugin</artifactId>
                <configuration>
                    <releaseGoals>
                        <releaseGoal>deploy</releaseGoal>
                    </releaseGoals>
                </configuration>                
            </plugin>
        </plugins>
    </build>

This solution worked for me. For more complex scenarios consult:
https://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html

[danielflower]

Closing as this is just a maven behaviour that can't be changed. Workaround: make sure every module has a reference to the plugin (either directly or via a parent), or call the goal with the full plugin name: com.github.danielflower.mavenplugins:multi-module-maven-release-plugin:release