## In replies all text above this line is added to the ticket ## Request received: maven 3.0.1 pulling in transient dependencies of a "provided" dependency as "compile"-scoped (ticket #21943)
Your request (#21943) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21943 ---------------------------------------------- Maven Users List, Dec-27 06:32 am (EST): i have a maven project that contains the following dependency: <dependency> <groupId>org.jboss.ejb3</groupId> <artifactId>jboss-ejb3-core</artifactId> <version>1.6.3</version> <scope>provided</scope> </dependency> this is part of a module that produces an ear artifact. according to the maven dependency scope doc ( http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html) the transient dependencies of a "provided"-scoped dependency are either scoped as "provided" or not treated at all. and yet in my case im seeing this as part of the build (produced with -X): [DEBUG] com.emc.illuminator:illuminator-ear:ear:6.0-SNAPSHOT [DEBUG] ...some direct dependencies edited out for brevity's sake... [DEBUG] org.jboss.ejb3:jboss-ejb3-core:jar:1.6.3:provided [DEBUG] javassist:javassist:jar:3.7.1.GA:compile [DEBUG] org.hibernate:hibernate-core:jar:3.3.1.GA:provided [DEBUG] antlr:antlr:jar:2.7.6:provided [DEBUG] dom4j:dom4j:jar:1.6.1:compile notice that javassist and dom4j are "upgraded" to compile-scoped, and they are also packaged as part of the ear. these are not the only artifacts "upgraded". this project builds just fine with maven 2. before i start adding a lot of exclusions, what am i missing here ? thanks in advance for any help/ideas/comments/clues, radai. -------------------------------- This email is a service from Boxee Support