[GRADLE-2931] Dependencies declared in a POM with the same groupId and artifactId but different type or classifier are treated as duplicates Created: 23/Oct/13  Updated: 24/Oct/13  Resolved: 24/Oct/13

Status: Resolved
Project: Gradle
Affects Version/s: 1.9-rc-1
Fix Version/s: 1.9-rc-2

Type: Bug
Reporter: Benjamin Muschko Assignee: Benjamin Muschko
Resolution: Fixed Votes: 1

Known Issue Of:


Reported via Gradle Forum.

We're running into issues when including the ch.qos.logback:logback-classic:1.0.13 jar into our projects.

It appears that 1.9-rc-1 isn't resolving POM dependencies correctly.
This is what the dependency report from 1.8 indicates:

+--- ch.qos.logback:logback-classic:1.0.13 
| +--- ch.qos.logback:logback-core:1.0.13 
| --- org.slf4j:slf4j-api:1.7.5

But 1.9-rc-1 generates this:

+--- ch.qos.logback:logback-classic:1.0.13 
+--- org.slf4j:log4j-over-slf4j:1.7.2 
| --- org.slf4j:slf4j-api:1.7.2 
--- com.h2database:h2:1.3.168

Comment by Scott Palmer [ 23/Oct/13 ]

This looks like it may be the issue I reported in

I found that revision 3b5c8e63b60f4815744516a6d3834f65ea1df3b5 was where the problem started.

Generated at Wed Jun 30 12:35:17 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.