I don't believe the doc covered pre-/post- lifecycle operations, just
the @aggregator changes that were the initial discussion.
They'd probably need a new proposal. Perhaps something hooking into
the model builder listening from the new work on trunk (just taking a
wild stab in the dark, haven't looked at it since they were introduced).
- Brett
On 15/12/2008, at 8:11 PM, Stephen Connolly wrote:
2008/12/15 Brett Porter <[email protected]>
On 12/12/2008, at 6:57 AM, Barrie Treloar wrote:
On Fri, Dec 12, 2008 at 3:51 AM, Brian E. Fox <[email protected]
>
wrote:
I think most of these ideas are already covered in the lifecycle
proposal out there that john wrote.
Can you paste the link in please?
http://docs.codehaus.org/display/MAVEN/Deterministic+Lifecycle+Planning
There are two linked docs at the bottom that are probably more
relevant.
It's not clear to me from that proposal, how we could accommodate
plugins
that need to update the pom...
For example, I'd like that versions-maven-plugin could work
preemptively for
goals like update-parent...
Perhaps some mojos will need a way to run outside the lifecycle, or
at least
signal that they could affect build plan determination somewhat... for
example, if I update the parent of some modules to a newer version,
that
newer version may add/remove profiles, add/remove plugins, etc.
Perhaps that is covered in the Wiki, but it's just not clear to me
-Stephen
- Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
