On 09/01/07, andy law (RI) <[EMAIL PROTECTED]> wrote:
Reading the ticket it seems there is a patch for this, although I'm not smart enough to work out where the patch is?
The patch is the file attachment 'maven-war-plugin-target-filename-path.patch' on that issue - it's a patch against the war plugin.
I've kind of got it working now using the assembly plugin, although *that* insists on naming everything with extensions rather than just generating the artifact with the name that one would hope it would use like I mentioned above. Perhaps the antrun method might not insist on doing that?
Is this the 'jar-with-dependencies' filename extension? The antrun method simply copies the applet jars across in their artifactId-version.jar filename format. I assume your method builds an 'uberjar' of your applet and it's dependency classes? The antrun method uses a manifest classpath to reference the dependencies as standalone jars.
In any case, using this method I have to create the webapp in two steps - firstly as a webapp that doesn't depend on the applet and then as a second webapp that depends both on the first webapp and also on the applet. I can't work out how to get mevenide/netbeans to deploy that auotmatically, but at least I have something that I can deploy manually.
Afraid I haven't used netbeans. Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
