[MEAR-49] 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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.3
• Flags: Patch
• Assignee: Stephane Nicoll
• Reporter: Ian P. Springer
• Created: 19/Nov/06 17:18
• Updated: 07/Apr/15 18:37
• Resolved: 10/Dec/06 10:58

Description

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.