Kevin,
I answered in your other mail, with pointers to sites partially
answering this question. Let me know if you need more information.
I'll add a little bit more here.
On 4/23/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote:
Hi Jerome,
Just a few questions to help me get my head around the difference between
the 3 different JNLP mojos and which one I should choose to use in a given
situation.
Same as for the assembly plugin
http://maven.apache.org/plugins/maven-assembly-plugin/usage.html
What does a 'parallel build lifecycle' mean in Maven terms?
It's a way to achieve several things: configure a mojo differently
accross multiple invocations in the same 'run', etc...
More details here:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
Is it something to do with forking as in Ant?
No
I've been trying to find documentation that explains what ${project} and
${executedProject} are referring to. Any pointers?
project and executedProject are filled up by Plexus (the IoC container
used by maven).
They are related to the POM. When you fork a cycle, you want to use
the executedProject instead of the project version of the POM, as your
project instance has been changed in the fork.
What does it mean to define a mojo as an aggregator? The plugin site says
that non-aggregators can be used multiple times in a single multi-module
build.
If you use single module, then your @aggregator mojo has no impact.
Does this mean that a given module can run the webstart plugin more
than once or that more than one module can run the plugin?
you mean the webstart:jnlp mojo ?
if you use it, it will run once for your whole aggregated
(multi-module) project.
Why are project artifacts not passed to parallel build lifecycles, e.g.
the JnlpMojo, which is defined as an executedProject? This causes the
webstart:jnlp goal to fail with a build error. In what cases would I use the
jnlp goal?
I've tried to match the way the assembly plugin works. You probably
need to use the jnlp-inline and attach it to your phase.
There are perhaps some things to change there... Haven't had the time
to work on it for a while...
Cheers,
Kevin
--
Jerome Lacoste
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
