One thing I don't like about most of the build systems is they tend to
end up being monster files.
In Ruby's, they let you drop a .rake file in a tasks directory and
rake tasks in there automatically are added to the main scope of rake.
What I'd really like are a bunch of different files based on their
functionality:
test.gradle, automation.gradle, etc
I know in 0.9 gradle is making it easier to add a bunch of groovy
classes to be imported by gradle, so maybe my focus should be having
leaner build.gradle and push out all the logic to groovy classes... ?
also (more importantly), as we are a product company, we have several
branches of code we work on simultaneously. I would also like to have
a master gradle build file and depending on which branch is active,
have the gradle build file pull in branch specific tasks. So I would
look at a properties file, see what branch is active and pull in tasks
to gradle from this branch.
Could someone point me to the "gradle way" to do this?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
