I've been playing with the use of the new build task in my company's projects
and in gradle's own build. I found a couple of issues that I would like to discuss:
1) The name 'build' unfortunately collides with Project.getBuild() when used
unquoted in a build.gradle. Since I think this task will be referred to
frequently, we need to resolve this. I really liked 'build' for the task you
would use most often :(. Any better ideas for yet another name? Anyone want to
support changing the Project.getBuild() method to something else?
2) The build task currently depends on dists. It seemed to make sense at the
time to build everything the plugin could. I tried using a more recent version
of the trunk to build gradle itself and updated explodedDistBase to depend on
'build' instead of libs. This caused an indirect circular dependency because
the allZip task (of type Zip) dependsOn explodedDist and the JavaPlugin adds all
Zip tasks to dists.
a) Should build have depended on libs instead? I had wanted to make and test
everything in this one task, but perhaps making the other zips is just overkill.
b) Should there be some way for Zip tasks to "opt out" of being included in
the dist task. Adding all jars and zips automatically to the libs and dists
tasks always seemed easy to use, but I've also always been a little
uncomfortable with this. It seems like the plugin may be assuming a little too
much here.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
