ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Hohn <>
Subject Re: Published jars for test, pilot, and production environments?
Date Tue, 19 May 2009 21:11:59 GMT

On Tue, 19 May 2009, Kirby Files wrote:

> Is there any reason not to use varying statuses for the different 
> environments?

This is a good solution if you can have separate downstream projects that 
fetch the JARs for each environment. If your situation is more complicated 
and you need to fetch different versions of an upstream JAR into the same 
downstream project for different purposes (unit test, deployment, etc.), 
look into Ivy configurations. They're designed to do exactly what you 

In our project we have a unit testing version of some of our projects 
(uses in-memory database support, etc.) and Ivy configurations let us grab 
one version of the JAR to run tests in the downstream and then grab a 
different version when it's time to package an EAR file.

Best regards,

View raw message