Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of aheritier@gmail.com designates
 209.85.216.177 as permitted sender)
References: 
 <CACxOcRqbBuSgnpqCbNtJwVjKS2gw9KpfPCJCnS57qzhdc+OxxQ@mail.gmail.com>
 <10600816.9262.1375005790481.JavaMail.mobile-sync@vecoo8>
From: =?ISO-8859-1?Q?Arnaud_H=E9ritier?= <aheritier@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <10600816.9262.1375005790481.JavaMail.mobile-sync@vecoo8>
Date: Sun, 28 Jul 2013 12:53:25 +0200
Message-ID: <744286017747773273@unknownmsgid>
Subject: Re: Changes in how exclusions are applied transitively ?
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 =E0 11:55, Stanimir Stamenkov <s7an10@netscape.net> a =E9c=
rit :

> [See my reply below the quote.]
>
> Wed, 24 Jul 2013 20:20:49 +0200, /Gr=E9gory 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org