Is it intended that in compare-gradle-builds the absence of a JAR in both builds is considered non-equal?


(Björn Kautler) #1

We have many subprojects and most share more-or-less the same structure which I inject by

subprojects{}

. This consists of 6 different JARs per subproject. But a specific subproject doesn’t necessarily have all 6 of them, this is controlled by

onlyIf { !sourceSets.a.java.empty || !sourceSets.a.resources.empty }

. Now if I do a compare-gradle-builds, I get various red entries because of JARs missing in both builds which essentially is identical and thus should be green, shouldn’t it?


(Luke Daley) #2

That’s a bug. Raised as GRADLE-2777.


(Björn Kautler) #3

https://github.com/gradle/gradle/pull/273 fixes this bug