Mark, > From: Mark Hobson [mailto:[EMAIL PROTECTED] > Sent: 10 January 2007 09:56 > To: Maven Users List > Subject: Re: Applets and assembly of webapps > > 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.
OK. So am I correct in thinking that in order to use this I need to get the code for the plugin, apply the patch, compile my own version of the plugin and use that in preference to the public released version? Or is there a less scary way of doing it. > > > 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. Yeah, that's the filename extension that I'm currently battling with. The maven docs all say 1 project, 1 jar and then the assembly plugin comes along and stomps all over that idea. Nice! I could even cope if it added the 'extension' before the version number. At least I could install that in my local repository and have my web app depend on/use the processed applet jar. But no. Nothing in life is easy. Because, let's face it, if it was easy then everyone would be doing it. > > > 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. Is there any way to 'inject' dependency file prior to a maven compile/install/deploy/whatever. I guess I'm looking for a process-resources type task that fetches a dependency jar (from somewhere) and puts it into the source tree so it gets included into the war file? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
