Manifest classpath ignores the "real" JAR filenames specified in <finalName> ----------------------------------------------------------------------------
Key: MJAR-61 URL: http://jira.codehaus.org/browse/MJAR-61 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Martin Desruisseaux The manifest classpath generated by Maven ignores the "real" JAR name as specified in {{<finalName>}}. For example the Geotools project tried the following configuration: {code:xml} <build> <finalName>gt-${artifactId}-${version}</finalName> {code} but the manifest classpath generated by Maven contains only {{${artifactId}-${version}.jar}} entries, which are non-existent JARs. *Note:* this problem happen only when the JAR dependencis come from the repository. The manifest classpath is correct if all dependencies were compiled in the same "{{mvn install}}" cycle. However this workaround is applicable only to Geotools developpers (in our case), because users of the Geotools library usually download the dependencies from a repository. This bug may be related to MJAR-28. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira