On 10/01/07, andy law (RI) <[EMAIL PROTECTED]> wrote:
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'm afraid that's it ;)
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.
The assembly plugin isn't really meant to be used for creating
dependencies for use with Maven. Have a look at the dependency plugin
for a better way of achieving this:
http://maven.apache.org/plugins/maven-dependency-plugin/
I haven't had a chance to switch my interim antrun solution over to
use this, but I gather this is currently the preferred solution.
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?
That's what I do with the antrun plugin - I use the Maven ant tasks to
bring the applet and it's dependencies down in the process-resources
phase. As suggested above, try using the dependency plugin to achieve
this in that phase.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
