[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_84132 ]
Rudyolph Bistrovich commented on MASSEMBLY-67:
----------------------------------------------
Don't you guys think it is an issue that depending on who did the deploy of the
snapshot and who is doing the assembly you will have different results? ie.
I wrote and deployed the snapshot and then do the assembly...dependency jars
come out with -SNAPSHOT
One of my developers does the assembly...dependency jars come out with the
datestamp.
We now have two flavours of assemblies zips that can wreak havok with
predefined classpaths.
It sounds like this is an issue with the deploy plugin itself since it should
be consistent no matter who actually did the deploy.
> 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
> Issue Type: Bug
> Reporter: Mark J. Titorenko
> Assigned To: John Casey
> Fix For: 2.2
>
> Attachments: MJAR-28-Notes.txt, MJAR-28-TestCases-Patch.txt
>
>
> 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
