I can see at least two alternatives to Maven-style snapshot development: 1. Use a multi-project build If the projects are versioned and released together, build them together. With Gradle's incremental build capabilities, this is much more feasible than it used to be. A multi-project build is also more reliable than throwing snapshots around because all of its subprojects are guaranteed to be based on the same source revision.
Projects hosted in different source code repositories can be brought together with something like Git's submodules, but think twice before going down that road. In the future, Gradle will support aggregate builds, a feature to facilitate going back and forth between building projects together, and building them separately. 2. Use Ivy's concept of "latest" version "latest.integration" seems to be Ivy's equivalent of Maven snapshots, but I haven't used it. See: http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.html That said, if Maven-style snapshot development works for you, then I don't see a reason to abandon it. It's just one "gradle install" away. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Blog: http://pniederw.wordpress.com Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/A-world-without-maven-snapshots-tp4461515p4479303.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
