Issue598901

classification
Title: Jythonc: dependencies on 3rd party jars
Type: Severity: normal
Components: Jythonc compiler Versions: Deferred
Milestone:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: fwierzbicki, tlau
Priority: low Keywords:

Created on 2002-08-22.17:40:52 by tlau, last changed 2009-03-13.23:20:09 by fwierzbicki.

Files
File name Uploaded Description Edit Remove
jython-externaljars.diff tlau, 2002-08-22.17:40:52 Patch to jythonc to enable specification of 3rd party jars
Messages
msg706 (view) Author: Tessa Lau (tlau) Date: 2002-08-22.17:40:52
When running a jar containing a standalone executable
using "java -jar", Java ignores any user-supplied
CLASSPATH and assumes that all user classes are
contained within the jar.  This behavior causes a
problem when a Jython program references classes
contained in a 3rd party jar file.  The program cannot
be run using "java -jar myprogram.jar" when it
references 3rd-party classes.  The temporary workaround
is to run the program using
"CLASSPATH=3rdparty.jar:myprogram.jar java myclass",
but this is ugly.

The proper way to address this problem is to have the
Jythonc compiler add an entry to the jar's MANIFEST.MF
file with lines like "Class-Path: 3rdparty.jar", which
will cause Java to look in the named jar files for
additional user classes.

I'm enclosing a patch against Jython 2.1 which adds an
"--externaljars" flag to jythonc that enables the user
to list the 3rd party jars on the jythonc command line
and adds the relevant entries to the manifest.
msg4256 (view) Author: Frank Wierzbicki (fwierzbicki) Date: 2009-03-13.23:20:08
jythonc is no longer maintained, and this is too implementation specific
to keep around.
History
Date User Action Args
2009-03-13 23:20:09fwierzbickisetstatus: open -> closed
resolution: wont fix
messages: + msg4256
nosy: + fwierzbicki
versions: + Deferred
2002-08-22 17:40:52tlaucreate