On 8/29/07, David Corbin <[EMAIL PROTECTED]> wrote:
> On Tuesday 28 August 2007 15:04:51 Jerome Lacoste wrote:
> > On 8/28/07, David Corbin <[EMAIL PROTECTED]> wrote:
> > > I'm trying to build the webstart plugin because I wish to enhance it. I'm
> > > actually able to checkout the trunk, and build the plugin. However I
> > > cannot get it to work.
> > >
> > > I have another project that uses webstart, and once I've installed the
> > > newly-built webstart plugin building my project just "glosses over" the
> > > webstart, never signing the jars required or producing any output.
> >
> > David,
> >
> > Did you use webstart plugin version 1.0-alpha-1 before you upgraded to
> > the latest snapshot ? If so you have to make sure you use the right
> > mojo. Some things changed after 1.0-alpha-1.
> >
> > I recommend that you carefully read the documentation here:
> >
> > http://mojo.codehaus.org/webstart-maven-plugin-parent/webstart-maven-plugin
> >/index.html
> >
>
> I looked through those, and identified two changes I need to make. One, which
> is to bind the plugin to the package phase, and that certainly makes it run
> where it wasn't before. The other seems like it has to do with location of
> the template.vm file, and I moved mine accordingly.
>
> However I'm still having problems. After some debugging, it thinks it has no
> dependency artifacts, which is clearly not true. As I understand it, it
> should start with a list of dependencies based on the pom.xml and the entire
> chain of other other pom.xml's dependencies. The <dependencies>
> configuration for this plugin then adjusts that list according to the
> includes/excludes
>
> Have there been any changes in the processing of the dependencies that should
> matter?
>
> I've attached a copy of the "mvn -X" output.
use the jnlp-inline mojo.
The jnlp mojo forks the build life cycle.
Cheers,
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
