I added the remaining exclusions to the component-matrix and it seems to have
removed all the remaining moles. I see what you are talking about where the
webservices modules has separate excludes defined. This is probably a bug in
Maven where dependencyManagement excludes are inherited, but regular dependency
excludes are not.
As a general rule, all the exclusion rules should be in the component-matrix.
That should help to avoid this type of issue.
Adrian Brock wrote:
On Thu, 2010-01-14 at 14:12 -0600, Paul Gier wrote:
> I think you will have to put excludes for both dependencies (with and without
> qualifier), since Maven will treat them as separate.
>
That's what I've done (in what I checked in).
It didn't work.
> Adrian Brock wrote:
>> I've been playing "whack-a-mole" trying to exclude the
>> references to org.jboss.microcontainer.
>>
>> But, I've got one strange one I can seem to exclude.
>>
>> I've tried excluding it on jbossws-framework and ejb3-common
>> (the latter is duplicated in the webservices project?)
>>
>> I think it has something to do with it having a qualifier in
>> component-matrix but not in the webservices pom?
>>
>> This is part of the output from "mvn dependency:tree"
>> in the testsuite.
>>
>> [INFO] +-
>> org.jboss.jbossas:jboss-as-webservices:jar:6.0.0-SNAPSHOT:compile
>> [INFO] | +- org.jboss.ws:jbossws-common:jar:1.2.2.GA:compile
>> [INFO] | +- org.jboss.ws:jbossws-framework:jar:3.2.2.GA:compile
>> [INFO] | \- org.jboss.ejb3:jboss-ejb3-common:jar:1.0.1:compile
>> [INFO] | \-
>> org.jboss.microcontainer:jboss-kernel:jar:2.0.0.CR5:compile
>> [INFO] | \-
>> org.jboss.microcontainer:jboss-dependency:jar:2.0.0.CR5:compile
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development