[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_70120 ] 
            
Baerrach bonDierne commented on MJAR-28:
----------------------------------------

Most of the comments I have made have been against MASSEMBLY-67 but the bug I 
believe is definitely in Maven Archiver (no bug has yet been raised for it)

MNG-775 doesn't affect this because:

- if the artifact is released this bug does not occur
- if the artifact is not deployed (only installed) then the correct value is 
-SNAPSHOT

so the only time this problem occurrs is when the artifact is deployed but not 
yet released.
If the artifact is deployed it has been placed in a repository with a 
timestamped snapshot version (complete with build number) and hence MNG-775 
does not apply.

My current work around is to manually rename the assembled artifacts to 
-SNAPSHOT.

The notes in MASSEMBLY-67 list the cause of the problem, the use of 
Project.getRuntimeClasspathElements() instead of using the runtime artifacts.

I'm looking into test cases now and should know more by the end of the week.

> 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

        

Reply via email to