[GRADLE-2068] archives built from configurations contain duplicate jars (M5->M6 regression) Created: 25/Jan/12  Updated: 04/Jan/13  Resolved: 08/Feb/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-6, 1.0-milestone-7
Fix Version/s: 1.0-milestone-9

Type: Bug
Reporter: Szczepan Faber Assignee: Daz DeBoer
Resolution: Fixed Votes: 0


 Description   

Originally reported at zendesk. To reproduce:

apply plugin: "java"

repositories {
	mavenCentral()
}

dependencies { 
	compile "org.apache.jackrabbit:jackrabbit-core:2.2.10" 
} 

task foo(type: Zip) {
	baseName = 'foo'
	from configurations.runtime
}

task wrapper(type: Wrapper) {
	//gradleVersion = '1.0-milestone-5'
	gradleVersion = '1.0-milestone-6'
}

/*
then:
  gradle(w) clean foo
  unzip -l build/distributions/foo.zip
*/
  • Expected: the zip contains single jackrabbit-spi-2.2.10.jar
  • Actual: the zip contains 2x jackrabbit-spi-2.2.10.jar

 Comments   
Comment by Daz DeBoer [ 08/Feb/12 ]

The root of the issue was that there are 2 transitive dependencies on jackrabbit-spi-2.2.10 declared in the jackrabbit pom files. One of these had no <classifier> element, while the other had an empty <classifier/> element.

http://repo1.maven.org/maven2/org/apache/jackrabbit/jackrabbit-spi-commons/2.3.7/jackrabbit-spi-commons-2.3.7.pom
http://repo1.maven.org/maven2/org/apache/jackrabbit/jackrabbit-core/2.3.7/jackrabbit-core-2.3.7.pom

We were incorrectly resolving these as 2 separate artifacts.

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