#19 Add Class-Path to Manifest

[Brian J. Sayatovic]

I suggest adding the classpath to the manifest.mf so
that the jar itself will be executable. I tested this locally
by hacking the manifest in treebeard.jar and it works
wonderfully (the following may look strange but it
is 'folded' at 70 characters as-per the manifest
specification):

Class-Path: . Ashpool.jar avalon.jar bsf.jar fop.jar js.jar
lax.jar re
gexp.jar treebeard.jar xalan.jar xercesImpl.jar xml-
apis.jar xmlParse
rAPIs.jar batik\batik-awt-util.jar batik\batik-bridge.jar
batik\batik
-css.jar batik\batik-dom.jar batik\batik-ext.jar
batik\batik-extensio
n.jar batik\batik-gui-util.jar batik\batik-gvt.jar
batik\batik-parser
.jar batik\batik-script.jar batik\batik-svg-dom.jar
batik\batik-svgge
n.jar batik\batik-swing.jar batik\batik-transcoder.jar
batik\batik-ut
il.jar batik\batik-xml.jar batik\batik.jar

Whthout this, you have to use an ugly batch file. With
it, you can just make a shortcut to Treebeard that uses
javaw.exe with the '-jar' option and the jar itself will
contain its own classpath so it will start.

[Rob]

Logged In: YES
user_id=570959

Good suggestion... I will get on this one

Cheers