Later occured to me that all dependencies have scope runtime. If I replace in b-pom.xml the scope with scope provided, all dependencies show up as provided, except the one that is actually scoped provided.
Can someone shed some more light on this? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, May 14, 2009 at 1:34 PM, Nick Stolwijk <nick.stolw...@gmail.com> wrote: > I have a strange issue with importing provided dependencies. > > I have a-pom.xml, which has a few dependencies and b-pom.xml which > imports a-pom.xml. > > After a mvn -f a-pom.xml install && mvn -f b-pom.xml dependency:tree I > see the following: > > [INFO] snapshot com.example:dependency-pom:0.1-SNAPSHOT: checking for > updates from atlassian > [INFO] [dependency:tree] > [INFO] com.example:example-jar:jar:0.1-SNAPSHOT > [INFO] \- com.example:dependency-pom:pom:0.1-SNAPSHOT:import > [INFO] +- commons-validator:commons-validator:jar:1.3.1:runtime > [INFO] | +- commons-beanutils:commons-beanutils:jar:1.7.0:runtime > [INFO] | +- commons-digester:commons-digester:jar:1.6:runtime > [INFO] | | +- commons-collections:commons-collections:jar:2.1:runtime > [INFO] | | \- xml-apis:xml-apis:jar:1.0.b2:runtime > [INFO] | \- commons-logging:commons-logging:jar:1.0.4:runtime > [INFO] \- oro:oro:jar:2.0.8:runtime > > These are all the dependencies which are in a-pom.xml except for: > <dependency> > <groupId>com.google.collections</groupId> > <artifactId>google-collections</artifactId> > <version>0.8</version> > <scope>provided</scope> > </dependency> > > Did I understand or do something wrong? > > With regards, > > Nick Stolwijk > ~Java Developer~ > > Iprofs BV. > Claus Sluterweg 125 > 2012 WS Haarlem > www.iprofs.nl > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
