On 02/07/2011, at 5:50 PM, cquinn wrote: > I am not sure if I am doing something wrong, or this is something missing in > Gradle. > > I am migrating an Ant+Ivy build system to Gradle, and in my experiments, my > uploads are uploading ivy files that are not resolved. That is, the orignal > dynamic rev values are still in place for the dependencies. WHat I would > expect (and what Ivy does during deliver) is that the rev value moves to > revConstraint, and then rev gets the static revision value. > > I'm currently seeing this with my little experiments, and using the Ivy > URLResolver and the GradleIBiblioResolver with the same results. > > Should Gradle be producing resolved Ivy files with static rev's and I am > just doing something wrong? Or, is this not supported (yet?) in Ivy?
This is not yet supported in Gradle. Could you add a jira issue for this? We plan to make some changes to the publication DSL (probably post Gradle 1.0 at this stage) which will allow the set of dependencies in the published ivy.xml to differ from the declared incoming dependencies. At the moment the published dependencies must be exactly the same as the incoming dependencies, revisions and all. On top of this, we will be able to provide something like ivy deliver, possibly as a default, or possibly as something you can easily enable. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
