[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_58158 ]
Mark J. Titorenko commented on MASSEMBLY-67:
--------------------------------------------
The issue title should read "assembling dependent jars that contain snapshots"
not "assembling dependent jars or snapshots".
This is still happening. I have a feeling that the assembly is doing the
correct thing while the jar plugin is not, so I'll also open an issue within
the jar plugin project and link it to this one.
This seems to occur when snapshot versions have been uploaded to the remote
repository. If snapshot versions exist within the local repository then
everything works out fine (jars are named version-SNAPSHOT in both plugins).
> assembling dependent jars or snapshots uses timestamp formatted version
> instead of ${version}
> ---------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-67
> URL: http://jira.codehaus.org/browse/MASSEMBLY-67
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Reporter: Mark J. Titorenko
>
>
> I'm using the jar plugin to add my dependencies to the manifest. I'm also
> using the assembly plugin to package all dependencies into one archive. The
> problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and
> the archiver adds them as "foo-20041113.jar".
> This causes my snapshot classes to not be found at runtime.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
