[mojo-dev] [jira] (MAPPASM-231) Use manifest-only jars for classpath

[Mark (JIRA)]

Title: Message Title

Mark commented on an issue   Re: Use manifest-only jars for classpath My current guess is that we just need a configuration option to specify the classpath manually. Produce classpath-only jar with: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <executions><execution><goals><goal>jar</goal></goals><phase>compile</phase></execution></executions> <configuration> <archive> <manifest> <addClasspath>true</addClasspath> <classpathLayoutType>repository</classpathLayoutType> <mainClass>my.main.Class</mainClass> <classpathPrefix>lib/</classpathPrefix> </manifest> </archive> </configuration> </plugin> And use maven-dependency-plugin to populate the lib dir. appassemabler can concentrate on generating the wrapper scripts, forget about classpath and lib aggregation. Add Comment   Mojo's AppAssembler Maven Plugin / MAPPASM-231 Use manifest-only jars for classpath All the messes with Windows pathname limitations and the ordering problems with wildcards could be eliminated by a manifest-only jar. That is, the plugin can create a jar file consisting only of META-INF/MANIFEST.MF, with entries for Class-Path: and Main-Class:, and then set up the script to run java -jar on it. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email