Re: Patch

From: Wilfred Springer <>
Date: Wed, 24 Oct 2007 16:33:08 +0200


I am not entirely sure if I understand what you're saying, but Farrukh
suggested to drop support for the Ant build completely. So if you want Maven
equivalents for these steps, most of that will be done automatically when
you do an official Maven release. Maven will build the a jar file containing
the sources and a jar file containing the binaries and upload all of that to
the Maven repository. It doesn't include the jar files upon which it depends
automatically. If you want that (and I can see why you would need that if
you want to continue to use the Ant task in projects that do not use Maven
yet) then there is a way to produce some additional artifacts as part of the

I could work on a solution that will (with every build) also build a zip/tgz
file containing the jar file and the dependent jar files, and upload that to
the Maven repository to with a release. I think that would address the needs
of people using Ant. They would download this collection of jars, copy them
over to their lib directory (or ANT_HOME/lib) and be in business.

Is this what you meant?


2007/10/24, Marc Hadley <>:
> On Oct 23, 2007, at 9:54 PM, Farrukh Najmi wrote:
> > * lib dir has been removed. This cuts out a lot of weight
> Forgive my Maven ignorance but how do the two distributions get built
> without the required jars, do the equivalent of the source-package
> and dist-package ant targets grab the required jars (for zipping with
> the wadl2java.jar) from a Maven repository as part of those build
> steps ?
> Marc.
> ---
> Marc Hadley <marc.hadley at>
> CTO Office, Sun Microsystems.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail: