Re: packaging jars vs. classes
On Wed, Nov 08, 2000 at 09:49:47AM -0500, firstname.lastname@example.org wrote:
> Aaron Brashears <email@example.com> writes:
> > After some reflection it seems that it would make more sense to just
> > copy the class files in /usr/share/java so setting the classpath for
> > standard packages would be handled once by setting
> > CLASSPATH=/usr/share/java once instead of having to tack on new jar
> > file to the classpath every time a new package is installed.
> Ah, wouldn't that be nice. If every package maintained compatibility
> release to release, we could do that. But that doesn't always happen.
> For example, Kawa's package hierarchy is going through some
> reorganization, such that if I compile BRL against Kawa 1.6.67 won't
> work with Kawa 1.6.70 (solved just by recompiling).
Good point. The current method of debanizing jars is going to fail
soon, since most I've run into don't version stamp the filename.
Joe Emenaker sent a nice idea to me which the list didn't get to
see. He suggested making a script which does autodetection of jar
files in your /usr/share/java and sets the classpath
appropriately. Though I don't think that the devault java
script/simlink/program should perform that kind of functionality, it
does sound like it would make a nice script that goes in java-common.