Re: Changes in how exclusions are applied transitively ?
[See my reply below the quote.] Wed, 24 Jul 2013 20:20:49 +0200, /Grégory Joseph/: I can't seem to find an accurate trace of this in the release notes, so I thought I'd just ping the list - Changes in how exclusions are applied transitively between Maven 2.2.1 and 3.1 ? Here's a situation: A has dependencies on B and C. Both transitively depend on D (through X, which is irrelevant, I think) but B excludes it (on its dep declaration of X) With 2.2.1, D was (wrongly imo) excluded from A (depending on dependency order, seemingly) With 3.1, it appears to behave correctly. Since I'm stuck with 2.2.1 for a bit, I'm facing a situation right now where I need to work around the bug, currently by removing the exclusions. That's currently OK, but at some point, those exclusions will be re-added (in A or in a new project) and we'll face the same issue again, without any clue as to why. How have people dealt with this so far ? I'm not sure I fully understand you, but I'm also stuck with Maven 2.2.1 currently, and I've noticed when excluding a transitive dependency it excludes it from other dependencies which have it as a transitive dependency. The other dependencies I don't want to exclude the transitive dependency from are either test or provided (needed only during build, actually). To workaround this I've declared the dependency I want to exclude as provided in a 'dependencyManagement' section, so it doesn't get included automatically in WAR and similar packages. See if this approach might help you, too. -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Changes in how exclusions are applied transitively ?
Maybe it is documented in aether release note ? We probably should add a link to it or include it in our release note. This is the problem to have a core component outside of the project. It makes it difficult to have a global overview of all changes done in the project itself and all its dependencies updates. - Arnaud Le 28 juil. 2013 à 11:55, Stanimir Stamenkov s7a...@netscape.net a écrit : [See my reply below the quote.] Wed, 24 Jul 2013 20:20:49 +0200, /Grégory Joseph/: I can't seem to find an accurate trace of this in the release notes, so I thought I'd just ping the list - Changes in how exclusions are applied transitively between Maven 2.2.1 and 3.1 ? Here's a situation: A has dependencies on B and C. Both transitively depend on D (through X, which is irrelevant, I think) but B excludes it (on its dep declaration of X) With 2.2.1, D was (wrongly imo) excluded from A (depending on dependency order, seemingly) With 3.1, it appears to behave correctly. Since I'm stuck with 2.2.1 for a bit, I'm facing a situation right now where I need to work around the bug, currently by removing the exclusions. That's currently OK, but at some point, those exclusions will be re-added (in A or in a new project) and we'll face the same issue again, without any clue as to why. How have people dealt with this so far ? I'm not sure I fully understand you, but I'm also stuck with Maven 2.2.1 currently, and I've noticed when excluding a transitive dependency it excludes it from other dependencies which have it as a transitive dependency. The other dependencies I don't want to exclude the transitive dependency from are either test or provided (needed only during build, actually). To workaround this I've declared the dependency I want to exclude as provided in a 'dependencyManagement' section, so it doesn't get included automatically in WAR and similar packages. See if this approach might help you, too. -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Changes in how exclusions are applied transitively ?
Hey there, I can't seem to find an accurate trace of this in the release notes, so I thought I'd just ping the list - Changes in how exclusions are applied transitively between Maven 2.2.1 and 3.1 ? Here's a situation: A has dependencies on B and C. Both transitively depend on D (through X, which is irrelevant, I think) but B excludes it (on its dep declaration of X) With 2.2.1, D was (wrongly imo) excluded from A (depending on dependency order, seemingly) With 3.1, it appears to behave correctly. Since I'm stuck with 2.2.1 for a bit, I'm facing a situation right now where I need to work around the bug, currently by removing the exclusions. That's currently OK, but at some point, those exclusions will be re-added (in A or in a new project) and we'll face the same issue again, without any clue as to why. How have people dealt with this so far ? Thanks for any hint or pointers ! -greg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Changes in how exclusions are applied transitively ?
Hey there, I can't seem to find an accurate trace of this in the release notes, so I thought I'd just ping the list - Changes in how exclusions are applied transitively between Maven 2.2.1 and 3.1 ? Here's a situation: A has dependencies on B and C. Both transitively depend on D (through X, which is irrelevant, I think) but B excludes it (on its dep declaration of X) With 2.2.1, D was (wrongly imo) excluded from A (depending on dependency order, seemingly) With 3.1, it appears to behave correctly. Since I'm stuck with 2.2.1 for a bit, I'm facing a situation right now where I need to work around the bug, currently by removing the exclusions. That's currently OK, but at some point, those exclusions will be re-added (in A or in a new project) and we'll face the same issue again, without any clue as to why. How have people dealt with this so far ? Thanks for any hint or pointers ! -greg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
