[ http://jira.codehaus.org/browse/MEAR-49?page=comments#action_80561 ] Stephane Nicoll commented on MEAR-49: -------------------------------------
How do we reproduce this unusual case? > if an artifact in the list of ear modules already exists in the ear, the ear > mojo will copy it on top of itself, zeroing out the file > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: MEAR-49 > URL: http://jira.codehaus.org/browse/MEAR-49 > Project: Maven 2.x Ear Plugin > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Ian Springer > Fix For: 2.3 > > Attachments: skip-already-deployed-module.patch > > > The ear plugin doesn't check for artifacts that are already deployed within > the ear, and so ends up redundantly copying such artifacts, e.g.: > copy C:/appserver/deploy/my.ear/lib/my.jar > C:/appserver/deploy/my.ear/lib/my.jar > and when you copy a file onto itself using the Plexus copy util method, it > zeros out the file (a bug in itself IMO but that's beside the point :). > A check should be added, so the ear plugin intelligently handles this, albeit > unusual, case. -- 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
