I'm fairly sure this didn't work in Maven 2.x. It was one of the unsolvable Maven 2.x bugs which was fixed in Maven 3. The workaround would be to use an older released version of the plugin. Don't think running a build twice is/was a workable workaround as I can't see how that would work in a release process.
/Anders On Mon, Sep 10, 2012 at 8:11 PM, Arnaud Héritier <aherit...@gmail.com> wrote: > On Mon, Sep 10, 2012 at 5:30 PM, Benson Margulies > <bimargul...@gmail.com>wrote: > >> On Mon, Sep 10, 2012 at 11:25 AM, Daniel Kulp <dk...@apache.org> wrote: >> > >> > On Sep 10, 2012, at 11:14 AM, Benson Margulies <bimargul...@gmail.com> >> wrote: >> > >> >> In Maven 2.x, the following was true; the reactor could not apply a >> >> plugin it had just built. So, if a particular problem required a >> >> plugin (e.g., for generating code), the plugin has to be an >> >> independent project that is built in advance. Is this still true in >> >> 3.x? >> > >> > I don't think this is/was true. CXF has always used it's own codegen >> plugins within its reactor build, even with Maven 2.x. >> >> Dan, I'll try it again, but I could have sworn that this only works by >> running 'mvn' twice, so that there's a SNAPSHOT in ~/.m2/repository. >> > > > I'm almost sure I had the same experience like Benson. > It doesn't work in one step because maven reads all projects in the > reactor, then tries to resolve the plugin where you are using it and cannot > because it was built. > > Arnaud --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
