I also liked it autobinding to the package phase,
because to enable it you still have to add the goal anyway.
And it's still possible to override the default phase anyway, by adding it.
I always do this in a seperate profile "production", to avoid slowing
down a normal "mvn install".
With kind regards,
Geoffrey De Smet
Jerome Lacoste schreef:
On 4/23/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote:
Hi Jerome,
Just letting you know that the reason the mojos are no longer binding to
the package phase is because the '@phase package' annotation has been
removed from the class javadoc.
I didn't think there was any point submitting a patch for it because it
would be simpler for you to just add it in directly. And I also wasn't
sure
if you had removed it intentionally.
I had removed it intentionaly. I redesigned to work like the assembly
plugin set of mojos.
You need to specify the phase. Probably need to update the doc...
See for http://maven.apache.org/plugins/maven-assembly-plugin/usage.html
for a rationale (Paragraph 'Building an Assembly as Part of the Build
Lifecycle').
As for the various jnlp mojos they are described in
https://svn.codehaus.org/mojo/trunk/mojo/webstart-maven-plugin/plugin/src/site/apt/index.apt:
Extract:
* Goals Overview
General Information about the goals.
* {{{jnlp-mojo.html}webstart:jnlp}} Packages a JNLP application.
* {{{jnlp-inline-mojo.html}webstart:jnlp-inline}} Packages a JNLP
application without launching a
parallel build lifecycle.
* {{{jnlp-single-mojo.html}webstart:jnlp-single}} Packages a JNLP
application in non-aggregator mode without launching a
parallel build lifecycle
Jerome
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
