Aha! rooting around for a bit, there is <classpathprefix> which prepends the "lib" part to each dependency. I'd have hoped that would be on the plugin homepage :( Cheers, Rich
________________________________ From: Richard Chamberlain [mailto:[EMAIL PROTECTED] Sent: Tue 04/12/2007 19:58 To: [email protected] Subject: custom manifest file still using dependencies Hi, I'm packaging my app in a zip. However if i want to use java -jar myapp.jar i have to include the dependencies in my manifest file. I've done this using: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifest> <mainClass> myapp.MainClass </mainClass> <addClasspath>true</addClasspath> </manifest> </archive> </configuration> </plugin> However there are > 20 dependencies and the manifest file requires them to be in the same directory. I'd like to put all my dependencies in a "lib" folder and have my manifest file locate them. It's neat that the manifest file gets generated from the dependecies, so i dont want to maintain my own manifest file. Ialso like the way that the dependencies are external to the jar. Can anyone help? Thanks, Rich --------------------------------------------------------------------- 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]
