On 03/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
What else would use it. I'm generally fine with things changing
provided you have the magic three. And can you think of any adverse
affects or conflicts with other phases. I can't think of any off the
top of my head but adding a new lifecycle is not something we can
ever take away once we do add it.

I assume jetty:run-war doesn't count as the third then? ;)
tomcat:exploded is another candidate for requiring pre-package phase
rather than the full package.

It would allow other mojos to contribute to the assembled package
before it's archived.  One example would be to produce an 'uberjar'.
The dependency:unpack-dependencies plugin could be bound to the
pre-package phase and then the jar plugin could then archive the
result in the package phase.

The only possible conflicting phases would be generate-sources and
generate-resources, since these phases also allow some manipulation of
the final package.  Although I think this phase provides a unique
extension point, since both those phases would be the wrong place to
perform package assembly actions such as those detailed above.

A related thread that also requires this functionality:
http://www.mail-archive.com/dev@maven.apache.org/msg62255.html

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to