[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351264#comment-351264 ] Daniel Wu commented on MNG-1977: It has been always a problem for anyone who hates common loggings :-) Really, this is a MUST-HAVE. Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven Issue Type: New Feature Components: FDPFC, POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-1977: --- Component/s: FDPFC Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven Issue Type: New Feature Components: FDPFC, POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342963#comment-342963 ] Radai Rosenblatt commented on MNG-1977: --- i just lost 2 days peppering my poms with individual exclusions. can we please have this feature? Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342902#comment-342902 ] Kees de Kooter commented on MNG-1977: - 8 years, 155 votes, 5 duplicates and 4 patches later I wonder: should I be proud or embarrassed that the issue is still unresolved? Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342923#comment-342923 ] Oliver Siegmar commented on MNG-1977: - This issue and MNG-624 (which is even older) are two reasons why I switched to Gradle. Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338250#comment-338250 ] Christoph Henrici commented on MNG-1977: A real world problem needs a solution. Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338250#comment-338250 ] Christoph Henrici edited comment on MNG-1977 at 1/8/14 9:19 AM: A real world problem needs a solution. Is there any real intention to adress this? was (Author: chenrici): A real world problem needs a solution. Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-1977: -- Fix Version/s: (was: 3.2) Issues to be reviewed for 4.x Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=318407#comment-318407 ] Neale commented on MNG-1977: JvZ - why not Maven 3.1 for this? It's highly voted and there's a patch, yet no comment on the patch has been made. That's not good for goodwill :( Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: 3.2 Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=311085#comment-311085 ] Jorg Heymans commented on MNG-1977: --- +1 to this, though i'm not sure if maven is still being actively developed ? Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven 2 3 Issue Type: New Feature Components: POM Reporter: Kees de Kooter Fix For: 3.2 Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277793#comment-277793
]
Jean-Noel Rouvignac edited comment on MNG-1977 at 12/11/11 5:22 PM:
@Arnaud Sorry, I went for the easiest to implement. If you do not like it this
way, fair enough, we can do it otherwise. I originally started with such change
to the pom.xml:
{code}project
dependencies
exclusions
exclusion
groupIdcom.mycompany/groupId
artifactIdmyproject/artifactId
classifieroptional/classifier
/exclusion
/exclusions
dependency
...
/dependency
...
/dependencies
...
/project{code}
No I did not test with older versions of maven.
I saw that maven-3 has got some validation mechanism for the scope so I think
it would reject it.
For maven-2 I need to check. Indeed the following scenario would be
catastrophic:
And when a maven version ignores it, what does it do ? It uses the compile
scope ? #fail in that case, instead of excluding it, you explicitely add it
(transitively).
I will test both of these and let you know.
Same, it does not really matter to me which mechanism you prefer to use. Just
tell me how you want it to look in the pom.xml and I can have a look at doing
it.
Jean-Noel
was (Author: jnrouvignac):
@Arnaud Sorry, I went for the easiest to implement. If you do not like it
this way, fair enough, we can do it otherwise. I originally started with such
change to the pom.xml:
project
dependencies
exclusions
exclusion
groupIdcom.mycompany/groupId
artifactIdmyproject/artifactId
classifieroptional/classifier
/exclusion
/exclusions
dependency
...
/dependency
...
/dependencies
...
/project
No I did not test with older versions of maven.
I saw that maven-3 has got some validation mechanism for the scope so I think
it would reject it.
For maven-2 I need to check. Indeed the following scenario would be
catastrophic:
And when a maven version ignores it, what does it do ? It uses the compile
scope ? #fail in that case, instead of excluding it, you explicitely add it
(transitively).
I will test both of these and let you know.
Same, it does not really matter to me which mechanism you prefer to use. Just
tell me how you want it to look in the pom.xml and I can have a look at doing
it.
Jean-Noel
Global dependency exclusions
Key: MNG-1977
URL: https://jira.codehaus.org/browse/MNG-1977
Project: Maven 2 3
Issue Type: New Feature
Components: POM
Reporter: Kees de Kooter
Fix For: 3.1
Attachments: global_excls_it-test_v2.patch,
global_excls_it-test_v3.patch, global_excls_maven3_v2.patch,
global_excls_maven3_v3.patch
I depend on some libraries, which in turn depend on something
(which in turn depend on something) that I don't want, because I declare
some other artifact in my pom.xml.
A concrete example: I don't want that the artifact xerces is imported in
my project because I declare to depend on xercesImpl which ships newer
libraries but with the same namespaces.
I guess I would need an exclude transitive dependency at all, either
globally or from this and that artifact. I saw the exclusions tag, but it
forces me to be very verbose and have exact control on what is required by a
dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Noel Rouvignac updated MNG-1977:
-
Attachment: global_excls_maven3_v3.patch
global_excls_it-test_v3.patch
Hello,
I gave another go at this issue.
This time, I specified the exclusions in the pom.xml file by following this
approach:
{code}
project
dependencies
...
/dependencies
...
exclusions
exclusion
groupIdcom.mycompany/groupId
artifactIdmyproject/artifactId
/exclusion
/exclusions
...
/project
{code}
Please let me know what you think of these patches.
Thanks,
Jean-Noel
Global dependency exclusions
Key: MNG-1977
URL: https://jira.codehaus.org/browse/MNG-1977
Project: Maven 2 3
Issue Type: New Feature
Components: POM
Reporter: Kees de Kooter
Fix For: 3.1
Attachments: global_excls_it-test_v2.patch,
global_excls_it-test_v3.patch, global_excls_maven3_v2.patch,
global_excls_maven3_v3.patch
I depend on some libraries, which in turn depend on something
(which in turn depend on something) that I don't want, because I declare
some other artifact in my pom.xml.
A concrete example: I don't want that the artifact xerces is imported in
my project because I declare to depend on xercesImpl which ships newer
libraries but with the same namespaces.
I guess I would need an exclude transitive dependency at all, either
globally or from this and that artifact. I saw the exclusions tag, but it
forces me to be very verbose and have exact control on what is required by a
dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1977) Global dependency exclusions
[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277611#comment-277611
]
Jean-Noel Rouvignac edited comment on MNG-1977 at 12/11/11 5:22 PM:
Hello,
I gave a go at this new feature following
Rob Elliot's idea of using a {code}scopeexcluded/scope{code}. And it works
a treat for me.
I uploaded the maven changes + integration test as patches.
Thanks,
Jean-Noel
was (Author: jnrouvignac):
Hello,
I gave a go at this new feature following
Rob Elliot's idea of using a
scopeexcluded/scope. And it works a treat for me.
I uploaded the maven changes + integration test as patches.
Thanks,
Jean-Noel
Global dependency exclusions
Key: MNG-1977
URL: https://jira.codehaus.org/browse/MNG-1977
Project: Maven 2 3
Issue Type: New Feature
Components: POM
Reporter: Kees de Kooter
Fix For: 3.1
Attachments: global_excls_it-test_v2.patch,
global_excls_it-test_v3.patch, global_excls_maven3_v2.patch,
global_excls_maven3_v3.patch
I depend on some libraries, which in turn depend on something
(which in turn depend on something) that I don't want, because I declare
some other artifact in my pom.xml.
A concrete example: I don't want that the artifact xerces is imported in
my project because I declare to depend on xercesImpl which ships newer
libraries but with the same namespaces.
I guess I would need an exclude transitive dependency at all, either
globally or from this and that artifact. I saw the exclusions tag, but it
forces me to be very verbose and have exact control on what is required by a
dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
