[GRADLE-406] possible bug around transitive dependencies Created: 19/Feb/09  Updated: 04/Jan/13  Resolved: 07/Apr/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.5.2
Fix Version/s: 0.6

Type: Bug
Reporter: Szczepan Faber Assignee: Hans Dockter
Resolution: Won't Fix Votes: 0

Attachments: Zip Archive simple-weather.zip    


Possible bug around transitive dependencies or my misunderstanding of gradle.

Gradle doesn't seem to download commons-collections:commons-collections:jar:3.1 which is a transitive dependency of velocity 1.5

Attached zip contains tiny project that has pom.xml and build.gradle (both are essentially the same). 'mvn test' builds fine (amazingly...) but 'gradle test' fails. One of the tests fails because commons-collections is not on the classpath. It seems commons-collections should be on the classpath because it is a transitive dependency of velocity.

Comment by Hans Dockter [ 07/Apr/09 ]

Hi Szczepan, the velocity pom in the maven repository is faulty. It sets its packaging to pom instead of jar. Therefore Ivy (and Gradle) can't deal with it.

See: https://issues.apache.org/jira/browse/VELOCITY-526

See also: http://markmail.org/message/ii3hgcqfgwce4bec

Maven seems to swallow this bug. Ivy spends a lot of effort in becoming very compatible with Maven. But there are warts which are hard to reengineer . Someone told me me that the policy for mavenCentral has changed. According to this person, they will allow now for fixing existing buggy poms.

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