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

[Mark (JIRA)]

Title: Message Title

Mark edited a comment 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, ie. replace the dynamically generated classpath with the classpath-only jar. Then produce classpath-only jar with: {code:xml}             <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>custom</classpathLayoutType>                             <customClasspathLayout>$${artifact.groupId}.$${artifact.artifactId}-$${artifact.version}$${dashClassifier?}.$${artifact.extension}</customClasspathLayout>                             <classpathPrefix>./</classpathPrefix>                         </manifest>                     </archive>                 </configuration>             </plugin> {code} And use maven-dependency-plugin to populate the lib dir. {code:xml}             <plugin>                 <artifactId>maven-dependency-plugin</artifactId>                 <executions>                     <execution>                         <id>copy-dependencies</id>                         <phase>generate-sources</phase>                         <goals>                             <goal>copy-dependencies</goal>                         </goals>                         <configuration>                             <outputDirectory>${jsw.output.directory}/lib</outputDirectory>                             <prependGroupId>true</prependGroupId>                             <useBaseVersion>false</useBaseVersion>                         </configuration>                     </execution>                 </executions>             </plugin> {code} appassemabler can concentrate on generating the wrapper scripts, forget about classpath and lib aggregation.     And as long as appassembler does not have the manual classpath setting option, you can use this workaround: {code:xml}             <plugin>                 <artifactId>maven-antrun-plugin</artifactId>                 <executions>                     <execution>                         <phase>compile</phase>                         <configuration>                             <target>                                 <replaceregexp file="${jsw.output.directory}/etc/wrapper.conf"                                                match="^(wrapper.java.classpath.2=).*$"                                                replace="\1lib/${classpath.only.jar}"                                                byline="true" />                                 <replaceregexp file="${jsw.output.directory}/etc/wrapper.conf"                                                match="^wrapper.java.classpath.[0-9]*=%.*$"                                                replace=""                                                byline="true" />                             </target>                         </configuration>                         <goals>                             <goal>run</goal>                         </goals>                     </execution>                 </executions>             </plugin> {code} 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