Import of pom dependencies incorrectly scopes dependencies as runtime
---------------------------------------------------------------------
Key: MNG-4029
URL: http://jira.codehaus.org/browse/MNG-4029
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.9
Reporter: Alex Deschapelles
Attachments: testparent.tar.gz
When dependencies are imported from a pom, they are resolved as runtime
dependencies in the importing project.
To test
1) Extract the attached project
2) cd into the testparent directory
3) mvn install
4) cd subparent/projectx
5) mvn dependency:resolve
This will bring back :
[INFO] The following files have been resolved:
[INFO] antlr:antlr:jar:2.7.6:runtime
[INFO] asm:asm:jar:1.5.3:runtime
[INFO] asm:asm-attrs:jar:1.5.3:runtime
[INFO] cglib:cglib:jar:2.1_3:runtime
[INFO] com.test:hibernate-deps:pom:0.0.1-SNAPSHOT:import
[INFO] com.test:spring-deps:pom:0.0.1-SNAPSHOT:import
[INFO] commons-collections:commons-collections:jar:2.1.1:runtime
[INFO] commons-logging:commons-logging:jar:1.1.1:runtime
[INFO] dom4j:dom4j:jar:1.6.1:runtime
[INFO] javax.transaction:jta:jar:1.0.1B:runtime
[INFO] junit:junit:jar:4.5:test
[INFO] net.sf.ehcache:ehcache:jar:1.2.3:runtime
[INFO] org.hibernate:hibernate:jar:3.2.6.ga:runtime
[INFO] org.springframework:spring:jar:2.5.6:runtime
It would be more appropriate if the resolved scopes matched what is in the pom
that defines them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira