[MNG-818] Ability to disable transitive dependency in a bundle artifact

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-1
• Fix Version/s: 2.0-beta-3
• Component/s: Artifacts and Repositories
• Environment: xp, linux
• Assignee: Brett Porter
• Reporter: Dan Tran
• Created: 01/Sep/05 01:09
• Updated: 05/Apr/15 23:36
• Resolved: 04/Oct/05 00:21

Description

There are 2 use cases:

• native-plugin can combine it built .o files with additional libraries on dependency list to produce a big bundle. However other native pom
  using bundle artifact will fail at link time ( linker not happy about duplicate referenes)

• I will have custom mojo to combine a bunch of jars on my dependcies list. However any pom file uses that bundle jar will have
  to carry extra jars with it.

Can we have a api method to trigger to install/deploy not to add the dependency artifacts in to pom??

Issue Links

• is duplicated by: MEAR-14 Transitive dependencies of War modules should not be copied in the Ear by default