[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_70051 ] Richard van der Hoff commented on MJAR-28: ------------------------------------------
Baerrach, have you been able to make any progress on this? Did you get an answer to your questions regarding the best way to fix this? We're suffering the same problem and would like to find a fix :/ http://jira.codehaus.org/browse/MNG-775 might make fixing this the "right" way rather difficult :( > Using the jar plugin with addClasspath and snapshots can create manifest > classpath with incorrect jar versions > -------------------------------------------------------------------------------------------------------------- > > Key: MJAR-28 > URL: http://jira.codehaus.org/browse/MJAR-28 > Project: Maven 2.x Jar Plugin > Issue Type: Bug > Affects Versions: 2.0 > Reporter: Mark J. Titorenko > > When the POM contains dependencies to snapshot versions of jars, and snapshot > versions of those jars are downloaded from a remote repository, the name of > the jar contained in the classpath added to the manifest, of the form > artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar > downloaded, which contains version information of the form > artifactID-X.X-YYYYMMDD.HHmmss-V.jar. > This does not affect snapshot versions which have been directly installed > into a local repository and have no uploaded version within the remote > repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar > form. -- 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
