× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. JAVA400-L
  3. March 2009

Re: Third party library locations (was: Java and OO Concepts)

David Gibbs skrev:
<app dir>/lib/log4j-1.2.3.jar
We spent some time thinking it over and found that this approach worked best for us. Our launch mechanism fires up <environment.dir>/<app>/app.jar which in the manifest links relatively to the various jars (which is then conventionally placed in lib).

This allows us to have multiple environments on the machine which does not interfere with each other. We found this to outweigh the advantages of sharing the jars across installations.

Preparing a new application takes some time in getting the jars right, and the manifest right, but as this is then considered static code, new deployments are fast and can be done from inside Eclipse.
I know people who prefer to keep the libraries in common system location ... which seems risky to me.
Would be interesting to hear their reasoning. I think they just haven't been bitten badly yet :)


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.