I've looked through the examples for this and it seems simple enough. 
However, I'd really like to have my classpath as a series of path elements 
for the sake of legibility and future maintnance, i.e.

<classpath>
        <entry>path1</entry>
        <entry>path2</entry>
        <entry>path3</entry>
</classpath>

instead of 

<manifest>
        <classpath>path1 path2 path3</classpath>
</manifest>

It may not seem like much in the simple example given here, but here's a 
class path from one of our production jars:

Class-Path: plugins/framework plugins/checkservices plugins/transferse
 rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap
 ps wcmPrincipals-hotfix.jar wcmPrincipals.jar securityUtil-hotfix.jar
  securityUtil.jar wcmCache-hotfix.jar wcmCache.jar  lib/apache/jakart
 a-commons/commons-cli-1.0.jar lib/apache/jakarta-commons/commons-coll
 ections-3.1.jar lib/apache/jakarta-commons/commons-dbcp-1.2.1.jar lib
 /apache/jakarta-commons/commons-lang-2.1.jar lib/apache/jakarta-commo
 ns/commons-pool-1.2.jar lib/apache/jakarta-commons/commons-logging-1.
 0.4/commons-logging.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswego.edu
 /util-concurrent-1.3.4.jar lib/jradius/jradius.jar lib/jradius/jradiu
 s-dictionary.jar lib/gnu/gnu-crypto.jar lib/httpclient/commons-codec-
 1.3.jar lib/httpclient/commons-httpclient-3.0.jar lib/emory.edu/backp
 ort-util-concurrent-2.2/backport-util-concurrent.jar lib/oracle/jdbc-
 10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1.0/jdbc_rowset_tiger1.
 0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.jar lib/rsa/authapi.jar 
 lib/apache/log4j/log4j-1.2.8.jar

So I'm sure you can see why I'd like the former approach. Any ideas would 
be welcome.


Thanks
Robert Egan

This email message and any attachments may contain confidential, 
proprietary or non-public information.  The information is intended solely 
for the designated recipient(s).  If an addressing or transmission error 
has misdirected this email, please notify the sender immediately and 
destroy this email.  Any review, dissemination, use or reliance upon this 
information by unintended recipients is prohibited.  Any opinions 
expressed in this email are those of the author personally.

Reply via email to