From: SourceForge.net <no...@so...> - 2006-05-11 19:23:24
|
Bugs item #598901, was opened at 2002-08-22 17:40 Message generated for change (Settings changed) made by fwierzbicki You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=598901&group_id=12867 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Jythonc compiler >Group: Deferred Status: Open Resolution: None Priority: 5 Submitted By: Tessa Lau (tlau) Assigned to: Nobody/Anonymous (nobody) Summary: Jythonc: dependencies on 3rd party jars Initial Comment: 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=598901&group_id=12867 |