commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Collins, Russell" <>
Subject RE: Question.
Date Fri, 11 Feb 2011 21:48:09 GMT
>From my experience, I try to use the latest and greatest.  As Joe said, most of the versions
do a good job of backwards compatibility.  My general rule of thumb is if there is a release,
replace the older one with the most recent in the development environment and see what happens
(run tests, etc).  Most releases do not take functionality away but will deprecate things
that are not longer relevant.  These changes are usually documented as well.  Using this strategy,
you can keep your application as up to date and as bug free as possible.  In my experience,
if there is something wrong with the new version, you will find out really quickly especially
if you are designing and testing your application properly.  It was also said earlier to use
Maven.  Trust me when I say that Maven can make this process of plugging in/reverting to different
assemblies VERY painless.  I used Ant for a long time and still like Ant very much.  After
using Maven however, I am now a believer!

Russell Collins
Sr. Software Engineer
CoreLogic Spatial Solutions

"Do or do not, there is no try." - Yoda

-----Original Message-----
From: Haswell, Joe []
Sent: Friday, February 11, 2011 3:20 PM
To: Commons Users List
Subject: RE: Question.

Hi Nadia,

In general, the various Commons releases maintain good backwards-compatibility with previous
releases between major versions (e.g. 2.x -> 3.x).  Most of those projects will probably
be in the latest major version, so keeping one jar on the classpath containing the latest
version of the necessary Commons component will /probably/ be safe /most/ of the time.  If
you're comfortable or already using Ant, consider using Ivy for dependency-management; if
you're not, I prefer Maven to Ant+Ivy.


Joe H. | HP Software

-----Original Message-----
From: Ayar, Nadia []
Sent: Friday, February 11, 2011 1:10 PM
Subject: Question.

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?

Please advise.

Nadia Ayar

Brokerage Services, Banking and Investment CGI Information Systems &
Management Consultants Inc. Office Phone Number - (905) 762 2800 X4502.
125 Commerce Valley Drive West - 6th Floor Markham, ON L3T 7W4

CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
to CGI Group Inc. and its affiliates may be contained in this message.
If you are not a recipient indicated or intended in this message (or
responsible for delivery of this message to such person), or you think
for any reason that this message may have been addressed to you in
error, you may not use or copy or deliver this message to anyone else.
In such case, you should destroy this message and are asked to notify
the sender by reply email.

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

This message may contain confidential or proprietary information intended only
for the use of the addressee(s) named above or may contain information that is
legally privileged. If you are not the intended addressee, or the person
responsible for delivering it to the intended addressee, you are hereby
notified that reading, disseminating, distributing or copying this message is
strictly prohibited. If you have received this message by mistake, please
immediately notify us by replying to the message and delete the original
message and any copies immediately thereafter.

Thank you.

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

View raw message