Message-ID: <475847832.4243.1369429882516.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4242_1008286387.1369429882516" ------=_Part_4242_1008286387.1369429882516 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
=C2=A0 Yesterday, during the explanation of the roadmap of maven=
2.1 in the meeting "Maven day", Jason said that a new setting wi=
ll be supported to exclude all the transitive dependencies.=C2=A0 I had eff=
ectively see numerous users that were complaining about the big exclusion l=
ist they have to maintain which is as annoying as in m1 for the list of all=
=C2=A0 My question : Is there someone who proposed to add a list of profile= s (We can use this term because we already use it in m2 but I don't have an= other idea today) in a dependency.
=C2=A0 For example for a complex librairie like Spring we can ask them t=
o create as many POM as they have usecases of this library. But it will be =
difficult to maintain.
=C2=A0 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 depend= ency 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------=_Part_4242_1008286387.1369429882516--