[MEAR-14] Transitive dependencies of War modules should not be copied in the Ear by default

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Environment: Win2k, Java 1.4.2, Maven 2.0 beta 1
• Assignee: Brett Porter
• Reporter: Fabrice Bellingard
• Created: 22/Sep/05 04:20
• Updated: 29/Mar/07 14:50
• Resolved: 22/Sep/05 04:29

Description

Currently, when an Ear is generated, every transitive dependency of its War modules is copied into the Ear, which makes them exist twice in the pacakge (one in the War and once in the Ear).
There's an 'excluded' property to prevent transitive dependencies of a War to be copied in the Ear, but this is painful because a War module usually have lots of dependencies.

So I would say that the packaging for an Ear should be more complex concerning the dependencies declared in its pom:

• for a Jar or an Ejb, then I agree that the transitive dependencies must be included in the Ear
• for a War, the default behaviour should be to include only the War itself, without all its transitive dependencies. There could be a property 'included' to tell the packager to take a specific dependency of the War and put it up in the Ear. (this would be the opposite behaviour as currently with the 'excluded' property)

Issue Links

• duplicates: MNG-818 Ability to disable transitive dependency in a bundle artifact
• is related to: MEAR-60 Improve support for skinny war files