maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Hardy <adam.ma...@cyberspaceroad.com>
Subject [m2] Dependency mistake in commons-dbcp?
Date Mon, 05 Sep 2005 23:12:31 GMT
I get this in my output

[INFO]
----------------------------------------------------------------------------
[INFO] Building MyStuff Login Module
[INFO]    task-segment: [eclipse:eclipse]
[INFO]
----------------------------------------------------------------------------
[DEBUG] org.mystuff:mystuff-login:jar:1.0-SNAPSHOT (selected for null)
[DEBUG]   junit:junit:jar:3.8.1 (selected for test)
[DEBUG]   commons-dbcp:commons-dbcp:jar:1.2.1 (selected for compile)
[DEBUG]     jdbc:jdbc:jar:2.0 (selected for compile)
[DEBUG]     junit:junit:jar:3.8.1 (setting scope to: compile)
[WARNING]
         Artifact junit:junit:jar:3.8.1 has scope 'test' replaced with
'compile'
         as a dependency has given a broader scope. If this is not
intended, use -X to locate the dependency,
         or force the desired scope using dependencyManagement.

[DEBUG]     junit:junit:jar:3.8.1 (removed - nearer found: 3.8.1)



It seems that commons-dbcp sets JUnit as a compile dependency:

http://www.ibiblio.org/maven2/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.pom

Surely this can't be right? I'd be glad to hear from anyone who helped 
put that POM together.

Regards
Adam

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message