[GRADLE-924] After build, the generated ivy.xml and pom.xml do not match in the build dir Created: 27/Apr/10  Updated: 04/Jan/13  Resolved: 24/Nov/10

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

Type: Bug
Reporter: Tomer Cohen Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Issue Links:
Duplicated by GRADLE-972 Gradle doesn't put a dependency secti... Resolved


After a successful build, looking at the ivy.xml and pom.xml in the build dir, there are no dependency decelerations in the generated ivy.xmls anymore, while the POM has all the info.

Looking at the .gradle/cache ivy.xml for a certain artifact contains all the relevant dependencies.
Also since the generated ivy.xml in the build dir is what is uploaded to a remote repo resolution via ivy will not work correctly (assuming there is no POM present).

Comment by Hans Dockter [ 05/May/10 ]

Is this fixed?

Comment by Tomer Cohen [ 06/May/10 ]

Not yet, I still get an ivy.xml in the build dir that only contains information about the artifact itself that was uploaded, without any information about its dependencies.

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