I hate manually adding 20 jar files to the classpath :-)
One of the much cleaner methods of doing this is to put your classes in a jar
file; then in the manifest file of your jar file use the 'Classpath' directive
to list the additional jars that *your* classes depend upon (i.e. those 20 jar
files). They can be entered relative to your jar file, or absolute.
This reduces the command line (and typing of it) greatly! Also, Java does a
pre-check at invocation time too, telling you if any jars you listed in that
directive are missing and aborting execution if there are missing jars.
This (the modifying the manifest) can all be done auto-magically if you're
using ant as a build tool.
--phil
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.