Hi all,
I wonder if custom lifecycle are still a thing or if extension (in
particular the ability to rewrite the pom before its processing) kind of
superseded them.
To be very concrete, it seems the DefaultLifecycleMapping order of the
mojos is not respecting the one from the components.xml and t
which looks like the one we're
already using in the components.xml
Robert
On Mon, 08 Feb 2016 23:33:54 +0100, Stephen Connolly
wrote:
So I was thinking somewhat about the issues with custom lifecycles.
One of the nice things I like about Maven is that the use of the standard
en.alan.conno...@gmail.com>:
> So I was thinking somewhat about the issues with custom lifecycles.
>
> One of the nice things I like about Maven is that the use of the standard
> lifecycles helps orientate new developers and prevents the sprawl of ANT
> targets.
>
> When I look a
phase we just force using that one... But
otherwise, yes we could blow up if there is a conflict... Though I like
namespaces to auto-select the project module subset to run on
>
> my 2 cents,
> Robert
>
>
> Op Mon, 08 Feb 2016 23:33:54 +0100 schreef Stephen Connolly <
> step
3:54 +0100 schreef Stephen Connolly
:
So I was thinking somewhat about the issues with custom lifecycles.
One of the nice things I like about Maven is that the use of the standard
lifecycles helps orientate new developers and prevents the sprawl of ANT
targets.
When I look at all the other bui
Op Mon, 08 Feb 2016 23:33:54 +0100 schreef Stephen Connolly
:
So I was thinking somewhat about the issues with custom lifecycles.
One of the nice things I like about Maven is that the use of the standard
lifecycles helps orientate new developers and prevents the sprawl of ANT
targets.
When
So I was thinking somewhat about the issues with custom lifecycles.
One of the nice things I like about Maven is that the use of the standard
lifecycles helps orientate new developers and prevents the sprawl of ANT
targets.
When I look at all the other build systems, what I keep missing in them
I added the following proposal to User Proposals a while back
http://docs.codehaus.org/display/MAVENUSER/Binding+Mojos+to+custom+LifeC
ycles+or+inclusion+of+the+Release+Plugin+LifeCycle+into+Maven+Core
And was just wondering whether there are any plans along these lines for
Maven 2.1?
William