ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <>
Subject Re: building with 3rd party libraries
Date Thu, 02 May 2002 15:49:02 GMT

----- Original Message -----
From: "John Gregg" <>
To: <>
Sent: Thursday, May 02, 2002 7:43 AM
Subject: OT: building with 3rd party libraries

> Hi all.
> I have a couple of off-topic questions that I'm sure you face all the
> First, when creating a war or jar file, do you include all 3rd party
> libraries necessary for your application to run/compile or not?

yes for a WAR, no for a jar

> libraries needed to run and those needed to compile aren't always the
> For example, you usually don't need jdbc drivers to compile but you do
> them to run.  Alternatively, you probably need servlet.jar to compile but
> not to distribute because your target environment already has it.

each lib component goes in its own lib subdir


with buildonly stuff in underneath


so castor/*.jar is the redist set; castor/**/*.jar the build set

> Second, of these 3rd party libraries, which do you keep in source control.
> All?


> Currently I'm keeping all 3rd party libraries in source control (well,
> except for the jdk stuff and servlet.jar), such as junit, our connection
> pool, etc.  They get labeled, built, and deployed like everything else.
> However, my current project runs on Tomcat and I like the idea that shared
> libraries can go in "common" and project-specific stuff can go under
> webapps/<project>/WEB-INF.  It seems silly of constantly "war-up" stuff
> very rarely changes.  Maybe the solution is that 3rd party stuff should go
> in source control but shouldn't automatically get included in the build.

doesnt add too much to the build :)

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message