Re: java library installation issues

[Bill Wohler <wohler@newt.com>]

> On 03 Apr 2001 07:50:33 +0200, Egon Willighagen wrote:
> I was playing around with a scheme; it went like this:
> -> versioned files and symlinks much like .so
> -> e.g. 
> ---> antlr-1.2.3.jar
> ---> antlr-1.2.4.jar
> ---> antlr-2.0.1.jar
> ---> antlr-2.1.0.jar
> ---> antlr-2.1.3.jar
> ---> antlr.jar -> antlr-2.1.3.jar
> ---> antlr-2.jar -> antlr-2.1.3.jar
> ---> antlr-1.jar -> antlr-1.2.4.jar
> 
> Then you have some wrapper script utlities to help you build a
> classpath. E.g. (pardon my scripting; I'm a Java programmer):

  Consider putting jars in /usr/share/java and slimelinking
  $JAVA_HOME/jre/lib/ext to /usr/share/java to get the jars for free
  without wrappers.

  If Sun's extension process is used in this fashion, you won't want
  to keep all the versions in this directory since antlr-1.jar will be
  used before antlr-10.jar, for example. Thus you might create
  /usr/share/java/package to hold all the versions of a particular
  package and slimelink /usr/share/java/package.jar to
  /usr/share/java/package/package-version.jar.

  Also note that you can have problems if you have the same classes in
  different jar files entirely. For example, my jserv installation was
  getting in the way of my tomcat compiles. But tomcat wasn't packaged
  at the time; the packaging scheme would most likely have resolved
  that issue (tomcat conflicts jserv).

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and mh-e. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.