Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.9
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Dependencies
-
Labels:None
-
Complexity:Intermediate
-
Testcase included:yes
-
Number of attachments :
Description
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.
Attached project seems to be broken (tar.gz contains only one binary file).