From: Dawid Weiss (Dawid.Weiss@cs.put.poznan.pl)
Date: Fri Jun 20 2003 - 03:10:50 PDT
Really? I think they are relative to the JAR where they are declared -
I used it numerous times with my code and it all worked well (but I never
checked this with other JVM's but SUN's):
java -jar ..\bubu\myjar.jar
load all the (relative) jar dependencies from ..\bubu even though the
currect directory remains to be '.'
>> So, in fact the xep35_server.jar should list the other jars in its manifest
>> file. To establish this you could do an experiment in which you add such a
>> manifest file to the XEP jar. The real solution is, of course, that the
>> manifest file is in one the future releases of XEP.
DT> A real problem with the real solution is that it is not possible to use
DT> relative paths in jar dependencies. That is, they are not relative
DT> to the jar they are specified in, but to the current directory.
DT> Thus, the only good option remains repackaging the .jar.
DT> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
DT> in the body of the message to firstname.lastname@example.org from the address
DT> you are subscribed from.
DT> (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to email@example.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Fri Jun 20 2003 - 03:12:28 PDT