Hi David:
I use a lot of 3rd party Jars.
For development I keep them in a common location. I update this
location as I add third party tools and the third party tools are
updated.
When I move my project into production I copy the third party Jars into
the application home folder where I put the applications jars. That way
I (or anyone else) know what jars (and their version) goes with what
project. When I update the production version I update the third party
Jars if necessary.
Bill Blalock
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Saturday, March 07, 2009 10:59 AM
To: Java Programming on and around the iSeries / AS400
Subject: Third party library locations (was: Java and OO Concepts)
Joe Pluta wrote:
... defeats at least part of the purpose of using third-party
packages in the first place
This made me think of a general question for folks ... Where do you
store 3rd party libraries? Do you keep them in a application specific
location or a common system location?
IOW ...
/usr/local/lib/log4j-1.2.3.jar
or
<app dir>/lib/log4j-1.2.3.jar
?
Personally, I prefer to keep the libraries in an application specific
location so I know that, when I deploy the app, the correct library
version is always the one I use.
I know people who prefer to keep the libraries in common system location
... which seems risky to me.
david
midrange.com
