Unfortunately not. To me it seems as if the reactor checks if everything is available and if it's missing the build fails. The strange thing is that it only checks if something is there ... during the build the freshly built version of the plugin is used ... it's just that maven gives up before even starting :-|
Chris ________________________________________ Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag von Anders Hammar <and...@hammar.net> Gesendet: Freitag, 12. September 2014 15:07 An: Maven Users List Betreff: Re: Releasing Maven Plugins > > The main problem is that the project contains the plugin as >> > >well as some modules that use the plugin. > This is the basic mistake in this scenario. If you build a maven-plugin > make a separate project from it and do the release etc. only from the > maven-plugin and afterwards you have the release available and can continue > with the rest which uses the release... Although I haven't tried it myself, my understanding is that it should be possible to use a plugin built within a multi-module project in some of the other modules when using Maven 3.x. This is not possible with Maven 2.x though. However, it requires the plugin to be built before the modules that uses it (which the reactor should be able to calculate, unless there are some circular module dependencies). /Anders > > > Kind regards > Karl-Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
