[
http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105948
]
Max Bowsher commented on MJAR-28:
---------------------------------
Todd: The local workaround that I'm using consists of:
1) Check out maven-archiver-2.2
Apply MNG-2456-maxb.patch
Deploy to local organization repository as (e.g.) 2.2-maxb-1
2) Check out maven-jar-plugin-2.1
Change maven-archiver dependency version in pom to 2.2-maxb-1
Deploy to local organization repository as (e.g.) 2.1-maxb-1
3) Reference maven-jar-plugin 2.1-maxb-1 in poms.
This is adequate when using maven-assembly-plugin 2.1. maven-assembly-plugin
2.2-beta-1 has broken things again though. (MASSEMBLY-211)
> 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
> Attachments: MJAR-28-patch.txt
>
>
> 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
