I see there's still a classpath statement in the 1.0 Manifest.mf file.
Is this necessary?  Could this be removed in the next version, and
document a classpath parameter to pass for manually executing?  I run
this with embedded code from an app which already has a classpath, so I
have to recompile as the manifest classpath interferes, and having this
classpath hardcoded prevents testing with updated versions of the
referenced jars.

Reply via email to