Right now we have an Ant build target that creates a dist dir like this:
dist/
theProject.jar
theProject.zip
lib/
log4j.jar
commons-httpclient.jar
...
theProject.jar contains all the classes based on the /src/java directory.
dist/lib/ contains all the jars you need to run our application.
theProject.zip contains the contents of dist/, minus the ZIP of course.
I know that I could probably call my Ant build from Maven, but then I'm not
sure how I would take advantage of the power of Maven to have dependent jars
automagically retrieved. Right now, the Ant script expects them to be in a
lib/ directory which lives in CVS.
K.C.
-----Original Message-----
From: Ashley Williams [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 14, 2005 12:11 PM
To: Maven Users List
Subject: Re: How do I package dependent jars in my distribution?
I also think there is a bunch of stuff missing out of the box after
the install/deploy phase - but then again other than a war and ear
distribution, I don't know how many other standard zips structures
there are. What sort of zip structure do you envisage?
AW
On 14 Sep 2005, at 20:00, KC Baltz wrote:
> I've searched the archives, seen this question asked a bunch, but
> never seen an answer I liked.
>
> We're just starting to look at Maven and I'd like to be able to
> produce a ZIP file that contains both the jar created from the
> source of our project as well as all the jars it depends on. Is
> there a good way to do this in Maven? Specifically, I'd love an
> example. Do any of the Jakarta projects do this with Maven?
>
>
>
> K.C. Baltz
> Java Developer
> 707-639-5337
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
