The root reason is because the "unbuilt" plugin *may* have a custom lifecycle that affects the reactor build plan in "ways unknown", and that could end up invalidating the build plan that is being constructed.
Now the custom lifecycles only come in if a plugin is marked as <extension>true</extension> so as long as you are not using a plugin built in your reactor as an extension we can know that the plugin does not affect the build plan! and thus we can continue... However, IIUC, flexmojos defines custom lifecycles and/or packaging and thus needs <extension>true</extension>, and therein is your problem. You'll need to split the release process so that the plugin is released independently On Friday, 12 September 2014, Christofer Dutz <[email protected]> wrote: > Unfortunately I've tried that :-( I can't start the build at all if the > plugin is not already in the repo as soon as a module intending on using > the plugin is in reactor. > > Chris > > > > ________________________________________ > Von: Robert Scholte <[email protected] <javascript:;>> > Gesendet: Freitag, 12. September 2014 17:08 > An: Maven Users List > Betreff: Re: AW: Releasing Maven Plugins > > Are you sure it's not pulled from the local repository? > To check, remove that SNAPSHOT and run 'mvn verify' and NEVER 'mvn > install'. > > Robert > > Op Fri, 12 Sep 2014 16:56:05 +0200 schreef Christofer Dutz > <[email protected] <javascript:;>>: > > > 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: [email protected] <javascript:;> <[email protected] > <javascript:;>> im Auftrag > > von Anders Hammar <[email protected] <javascript:;>> > > 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: [email protected] > <javascript:;> > >> For additional commands, e-mail: [email protected] > <javascript:;> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > <javascript:;> > > For additional commands, e-mail: [email protected] > <javascript:;> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected] > <javascript:;> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected] > <javascript:;> > > -- Sent from my phone
