[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

["Todd Nine (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105944 ] 

Todd Nine commented on MJAR-28:
-------------------------------

I'm also experiencing this.  We're working on a huge project with about 15 sub projects.  This really causes problems with our deployable artifacts.  Is there anyone working on it?  If not, where would I begin looking to fix this?

> 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