[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Environment variables for Debian (e.g. JAVA_HOME, etc)



Well there is, $JAVA_HOME/lib/ext, but that is global for everyone
and is within the Java directories so if you install a new version you
have to move your JARs across.  

I tend not to use it except for things that I really want to be globally
available (like the Postgres JDBC jar), but its there if you want to use
it.  

Similarly if you have things that all webapps on Tomcat want to 
use there is common/lib and common/endorsed.

David

On Thursday 09 September 2004 07:15, Peter Samuelson wrote:
> [Matthew Palmer]
>
> > Or Java could be sensible and have a standard place for putting
> > libraries that you didn't have to specify via an environment
> > variable. Then you wouldn't even need a wrapper...
>
> I have wondered for *years* - first, why Java doesn't do this, and
> second, why Java users don't seem to see a problem with Java not doing
> this.  By and large they seem to just accept calmly that you have to
> set arcane variables just to run any and all programs.  This is like
> having to have LD_LIBRARY_PATH in your environment in order to run ls.
>
> A mystery indeed.
>
> Peter



Reply to: