You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2013/11/09 20:33:20 UTC

[jira] (MEAR-149) skinnyWars and SNAPSHOT unique dependencies

     [ https://jira.codehaus.org/browse/MEAR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MEAR-149.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.8.1)
                   2.9
         Assignee: Robert Scholte

I've added a parameter so users can still use the baseVersion if they want. By default the version is used. This is the same as for other plugins which have this option.
Fixed in [r1540373|http://svn.apache.org/r1540373]
                
> skinnyWars and SNAPSHOT unique dependencies
> -------------------------------------------
>
>                 Key: MEAR-149
>                 URL: https://jira.codehaus.org/browse/MEAR-149
>             Project: Maven Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.7
>         Environment: All
>            Reporter: Seth Rife
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 2.9
>
>         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
For more information on JIRA, see: http://www.atlassian.com/software/jira