Looks good Mauro. Thanks.
kool :-)
My only comment is about the "category" addition to a dependency. Can you
explain the usage of this with an example?
This was used to create distros in which the libs were meant to go in more than a single directory.. Eg,
http://jcontainer.cvs.codehaus.org/viewcvs.cgi/*checkout*/jcontainer/loom/distribution/project.xml?content-type=text%2Fplain&rev=1.23&root=jcontainer
Different jars serve different purposed in the binary distro,
so we wanted to deploy them in separate directories,
whose path is only dependent on the nature of the distribution.
So specifying the categories as container:container/lib,shared:lib,tools:tools/lib
tells the plugin to put the libs of container category in container/lib,
the shared libs in lib/ and the tools libs in tools/lib.
The result of this distro is in http://dist.codehaus.org/loom/distributions/
This may not be needed by everyone, but in more complex distribuitions it provides quite a handy way of deploying the libs.
My impression was that the form of copying out of the "jars" directory should not be done, and instead use ${dependency.path}, to allow for jar overrides.
You mean, using
<ant:include name="${dependency.path}"/>
in place of
<ant:include name="${dependency.artifactDirectory}/jars/${dependency.artifact}"/>
<ant:include name="${dependency.artifactDirectory}/licenses/${dependency.artifactId}.license"/>
It would work for the jar, but how would you copy the license?
Cheers, Mauro
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
