Bret Marzolf wrote: > > In the short time I've worked with Gradle, I've gotten the sense that > Gradle expects that your gradle.build file is at the top level of your > project source tree but what if you wanted to set things up such that > gradle.build was in one location and all of your project source were > somewhere completely different? I tried changing > rootProject.projectDirectory in the settings.Gradle but that didn't seem > to do it for me. >
The only restriction that I'm aware of is that you need to invoke Gradle in a way so that it can find settings.gradle. See the Gradle User Guide for the details. Everything else should be completely customizable. However the correct syntax is 'rootProject.projectDir = new File(...)' rather than 'rootProject.projectDirectory = ...'. Bret Marzolf wrote: > > Along the same lines, how do folks typically tie into CI build tools with > respect to getting project source files downloaded from your version > control system prior to building? Do you have one build file that contains > a download task and a task that executes a separate gradle.build file > that's collocated with your project source? > All the CI servers I've worked with (TeamCity, Hudson, Bamboo) take care of checking out sources themselves. Gradle only kicks in afterwards. This means that all Gradle build scripts can be put under source control. If you use a CI server, make sure to have a look at the Gradle Wrapper. It's well documented in the Gradle User Guide. -- 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/Externalizing-build-scripts-CI-build-tool-integration-tp4410807p4414046.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
