Might also want to look at this on the wiki for a simple example http://docs.codehaus.org/display/GRADLE/Plugins#Plugins-ExampleofasimplecustomtaskwithinbuildSrc
Philip On Wed, Jun 16, 2010 at 4:55 AM, Adam Murdoch <[email protected]> wrote: > On 16/06/10 6:43 PM, Jim Cross wrote: >> >> Hi, >> >> We're writing a gradle script to build and deploy our system. The >> deployment bit is quite involved, so we've extract some of the logic into >> classes in the script. We'd now like to pull these classes out into top >> level groovy classes. When I've pulled out these top level classes, how do I >> put them on the gradle script's classpath? The only similar thing I can find >> in the docs is to package them into a library and add the library to the >> classpath. Is there a better way to do this? >> > > You can add them to the buildSrc/src/main/groovy directory, and they will > get compiled and included in the script classpath. > > There's an example of this in $gradleHome/samples/java/multiproject and you > can find some more information at > http://gradle.org/0.9-preview-3/docs/userguide/organizing_build_logic.html#sec:build_sources > > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > CTO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
