Yesterday, during the explanation of the roadmap of maven 2.1 in the meeting "Maven day", Jason said that a new setting will be supported to exclude all the transitive dependencies. I had effectively see numerous users that were complaining about the big exclusion list they have to maintain which is as annoying as in m1 for the list of all the dependencies.
My question : Is there someone who proposed to add a list of profiles (We can use this term because we already use it in m2 but I don't have another idea today) in a dependency.
For example for a complex librairie like Spring we can ask them to create as many POM as they have usecases of this library. But it will be difficult to maintain.
Or we could do something like :
In the POM of MyHorribleProjectWithALotOfOptionalDependencies
It's something more fine than the optional element.
In the POM of my project which uses this framework, I can use the dependency without profile :
To get all the dependencies.
I can use the profile-1
To get lib-A, lib-C, lib-D
I can use the profile-2 to get lib-B, lib-C, lib-D