Interesting… I wonder how I've managed to do CXF releases for all these years then. :-)
Seriously, for CXF <=2.5.x, I use Maven 2.2.1 and it "just works". Parts of the build certainly do use the plugins that are built as part of the reactor. That said, we use "install" as the default target and not test or anything. I'm fairly certain it wouldn't work if we didn't use install as the target, but I'm not sure if that would work with 3.x either. The "clean" target doesn't work if the plugin is part of the reactor and not in .m2/repository. I'll give you that. Dan On Sep 10, 2012, at 2:59 PM, Anders Hammar <and...@hammar.net> wrote: > 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 > -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
