First some remarks: 1. If at all, version ranges make sense in the deployed POM. Use concrete versions in your build script. This ensures that you know what you are compiling against, and that the dependencies (and hence your build!) won't change without explicit action from your side. 2. Version ranges are rarely used in the Maven world, presumably because they work better in theory than in practice.
Now to your question. There are several hooks for customizing POM generation. See "Example 34.7. Modifying auto-generated content" in the user guide. The next question is how to get the resolved dependencies and match them against the POM. I think that Configuration.getResolvedConfiguration() is the key, but the solution will require some coding. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Founder, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Need-help-determining-resolved-dependency-versions-when-uploading-with-mavenDeployer-tp3365591p3365611.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
