Hi Brant, i think i don't fully understand. If you want to bundle your application JAR with its dependencies you can use the uberjar plugin (part of the standard maven distro) or the javaapp plugin (http://maven-plugins.sourceforge.net/maven-javaapp-plugin/index.html). I've found the javaapp plugin working better (although uberjar is certainly more sexy ;).
Using the classpath-entry of the manifest-file for this is usually more tricky, as the entry is dependent on the location of the dependencies. So far I've only used it for EJB-JARs in EARs. Another way of doing this is shipping the dependencies in a lib/ dir and providing a start-script. -Stefan > -----Original Message----- > From: Brant Gurganus [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 22, 2004 3:18 AM > To: [EMAIL PROTECTED] > Subject: dependencies/JAR > > > How do other projects deal with moving dependencies to the build > directory and adding them to the classpath entry of the generated JAR? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
