[
https://jira.codehaus.org/browse/MEAR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308524#comment-308524
]
Geert Schuring edited comment on MEAR-149 at 9/14/12 9:15 AM:
--------------------------------------------------------------
I'm running into this problem, and I must say that I'm quite stunned that this
kind of bug is still present in the 2.8 version of the maven ear plugin,
especially when there's a patch available that solves it. Could you (any
committer) release 2.8.1 that includes this patch?
Some detail about our situation: Because some jar is present twice in the ear
file (once in ear file, and once in embedded war file), Weld throws an
exception because it finds 2 candidates for 1 injection point and our ears
cannot be deployed on our application server (Glassfish 3).
was (Author: cathodion):
I'm running into this problem, and I must say that I'm quite stunned that
this kind of bug is still present in the 2.8 version of the maven ear plugin,
especially when there's a patch available that solves it. Could you (any
committer) release 2.8.1 that includes this patch?
> skinnyWars and SNAPSHOT unique dependencies
> -------------------------------------------
>
> Key: MEAR-149
> URL: https://jira.codehaus.org/browse/MEAR-149
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: All
> Reporter: Seth Rife
> Priority: Minor
> Fix For: 2.8.1
>
> Attachments: ear-snapshot-dependencies.txt
>
>
> When trying to create skinnyWars, any SNAPSHOTS dependencies are not
> extracted out of WARs that have SNAPSHOT dependencies with unique timestamps.
> The AbstractFileNameMapping class uses the baseVersion to generate the
> filename which doesn't take into account timestamp dependencies, therefore
> the plugin is unable to delete any dependency in the libDir folder. Using the
> Artifact.version property will produce the correct filename for deletion.
> The really only affects DEV-produced artifacts where EARs are built for
> deployment and testing. Additionally, bloated EARs can affect repository
> managers where excessive disk space may not be available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
