> > 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.
Coincidentally (or not), I *just* stumbled across this plugin and have
used it to stuff a version of the applet into my war file, so at least
that problem is partially fixed. There are the usual idiosnycratic (to
my mind) issues in the configuration of this plugin and the way it slots
into the lifecycle, but that is something that I can work around.
So I'm comfortable with working with the dependency plugin to copy
artifacts to locations in the *file* system, but I still need to work
out how to get them some place where they will be included in the jar
file.
There's also the issue of having to code dependencies twice, once as a
proper dependency and once more in the dependency copy configuration
section?
Perversely, the artifacts with dependencies that the assembly plugin
generates do seem to get deployed into my local repository but I cannot
reference tham in any way. Is there *any* way to specify that I need to
get abc-applet-{$version}-with-jar-dependencies rather than
abc-applet-{$version}? That would (potentially) solve all of my
problems.
>
> > 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.
As I said above, I've nailed (I think) the injecting into the war file
bit now. Thanks for your help.
Later,
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
