commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Farrukh Najmi <>
Subject Re: Question.
Date Fri, 11 Feb 2011 20:15:19 GMT

Using maven for dependency management of your project is a huge step in 
the right direction:

Maven typically will replace ant for build management and provide much 
more value beyond that.

On 02/11/2011 03:09 PM, Ayar, Nadia wrote:
> Hello Common Developers,
> In my department, we have java modules on Unix, some of them uses third
> party tools like:  jasper, some uses hibernate, .... .  Some modules
> uses more than one java third party tool.
> Most of these third party tools uses commons in their code. Now we
> install all of these products in order Unix box and change the class
> path in order to use the third party tool in our modules.
> The question is how to control different releases of commons within the
> same program? How compatible are your new releases with the older ones.?
> Is it safe to substitute always with the latest for all these third
> party tools?

Farrukh Najmi


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

View raw message