[ 
https://jira.codehaus.org/browse/MEAR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296745#comment-296745
 ] 

Paul Vonnahme commented on MEAR-149:
------------------------------------

I'm also seeing this issue. 

I'll also point out that if the person who built the war was using 
<outputFileNameMapping> feature of the war plugin, the ear plugin may not match 
any of the file names. Maybe you will need to have a 
<skinnyWarOutputFileNameMapping> option? Or would it be possible to pull the 
mapping from the war's pom.xml? In any case, I see that as a smaller issue than 
the SNAPSHOT dependencies. Ideally for now this patch could be applied, and 
support for <outputFileNameMapping> could be deferred if it's more of a major 
undertaking.

In any case, the <skinnyWars> option is a great feature to have and I'm excited 
to see it mature.
                
> 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
>         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

        

Reply via email to