We've been trying to resolve this issue for a while now(See Java bug
reports #4339262 and #4430150). Most of the solutions we considered
are real pain to maintain to say the least. But recently a member of
our group stumbled upon Sun's Extension Mechanism Architecture:
http://java.sun.com/j2se/1.3/docs/guide/extensions/spec.html
Below is the guote from that spec:
"...For example, given the following class path:
a.jar b.jar
If optional package b.jar contained the following Class-Path manifest
attribute:
Class-Path: x.jar a.jar
Then, the resulting application class path would be the following:
a.jar b.jar x.jar
Of course, if x.jar had dependencies of its own then these would be
added according to the same
rules and so on..."
Thus we can create a .jar file which has nothing but a "link" to all
other .jars and only that one .jar goes into CLASSPATH. Amazing hah!
We performed some preliminary tests and it worked. The thing we
haven't tried yet is all different scenarios of what happens when we
have .jars that have the same names but located in different places
and other issues related to "duplicate" .jars. But this is a different
can of warms related to versioning problem.
Hope this helps,
Oleg Pariser @ NASA-JPL Multimission Image Processing Lab
[EMAIL PROTECTED]
>Hi,
>
>sorry this question is off topic and not related to Java3D.
>I am working under Solaris in a tcshell and tried to expand my
>classpath. Okay it is very long about 12 lines and now the shell states
>"word too long" during source .tcshrc. Is there a limitation for the
>length of the classpath variable?
>
>Thanks Desiree
>
--
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
