[
https://jira.codehaus.org/browse/MEAR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345954#comment-345954
]
Stephan Pauxberger commented on MEAR-179:
-----------------------------------------
I can confirm this behaviour. The plugin seems to ignore "useUniqueVersions"
archiver directive (perhaps a problem in a newer archiver version). This
completly broke our deployment. (Websphere, we include classpath in ejb-module
MANIFEST files, pointing to SNAPSHOT versions, since with 2.9 the artifacts are
timestamped, classpath does not match real files, so the deployment fails).
Downgrading to 2.8 solved it for now.
> Timestamped jars (sometimes)
> ----------------------------
>
> Key: MEAR-179
> URL: https://jira.codehaus.org/browse/MEAR-179
> Project: Maven Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.9
> Environment: Hudson 3.1 on Redhat Linux.
> Reporter: Morten Knudsen
>
> I upgraded Maven ear plugin from 2.8 to 2.9. After that some *but not all*
> SNAPSHOT dependencies are included with the timestamp in their names.
> This was not the behaviour in 2.8. I have not found any pattern in which
> dependencies that use snapshot and which that don't.
> 2.8:
> [INFO] Copying artifact
> [jar:dk.autocom.invoice.pdf:invoice-pdf-core:2.40-20140121.141224-7] to
> [lib/invoice-pdf-core-2.40-SNAPSHOT.jar]
> 2.9
> [INFO] Copying artifact
> [jar:dk.autocom.invoice.pdf:invoice-pdf-core:2.40-20140121.141224-7] to
> [lib/invoice-pdf-core-2.40-20140121.141224-7.jar]
> Is this the intended behaviour?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
