Why do you do a new checkout on every build? Are you trying to automate a release procedure?
Sean Van Buggenum wrote: > > But is there a way to declare the source of the code (i.e., a subversion > repository) and get it to build automatically from there? > Have you considered using a continuous integration server (TeamCity, Hudson/Jenkins, etc.) for this? Sean Van Buggenum wrote: > > Do I need to build this up myself, in the way I would anyway using Ant, > (checkout myself, creating folders, programmatically selecting branch etc) > Gradle doesn't yet ship with plugins for interacting with version control systems. But that's usually just a tiny part (if at all) of what a build does. So there's still a big difference between using Gradle and Ant. Also it is much easier to implement custom tasks and workflows with Gradle/Groovy than with Ant/Java/XML. For example, here is a small abstraction that allows Gradle's own build to interact with Git: https://github.com/gradle/gradle/blob/master/buildSrc/src/main/groovy/org/gradle/build/Git.groovy -- 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/subversion-and-gradle-multiple-project-build-tp3360812p3361661.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
