On Tue, Sep 11, 2012 at 3:19 AM, Anders Hammar and...@hammar.net wrote:
Switch to Maven 3 and this should work. Try it and report back!
I did and it did.
/Anders
On Mon, Sep 10, 2012 at 11:22 PM, David Jencks david_jen...@yahoo.com wrote:
Our experience in geronimo has always been that
the plugin in my repo and from then
on the updated plugin is used.
So I think you are all right.
Chris
-Ursprüngliche Nachricht-
Von: Benson Margulies [mailto:bimargul...@gmail.com]
Gesendet: Dienstag, 11. September 2012 12:17
An: Maven Developers List
Betreff: Re: the simplest possible maven
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?
On a related front, have any
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
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.,
On Mon, Sep 10, 2012 at 5:30 PM, Benson Margulies bimargul...@gmail.comwrote:
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
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
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
Our experience in geronimo has always been that maven does not support this,
and I thought for maven 3 it was announced that it never ever would.
We have a proflie to build up through the plugin, then you can do the full
build.
Releasing is a pain as you have to do the manual profile build
