On Aug 14, 2009, at 8:03 AM, Paul Speed wrote:
<snip>
This is probably not related but my only other project pain has to
do with the compile test cycle.
It used to be that we had some junit helper classes that depended on
our util module. The util tests used these helper classes to test
the util classes. In Ant this was ok because all project source was
compiled and then all test code was compiled and run.
In gradle (and maven, and etc., etc. any other project-based build
system), each project is an island and must be "fully built" before
another project gets to use it. This adds a sort of artificial
circular dependency since to compile the junit helpers one must full
build util which includes testing the jar which requires the junit
helpers, etc..
It's sort of too bad that project -> project dependencies can't have
their tasks interleaved such that I'd get util:compile,
junit:compile, util:test, junit:test, etc..
This is absolutely possible with Gradle. In Gradle project
dependencies are just syntactic sugar and they are translated into
cross-task dependencies. The problem with your use case was that our
jar tasks depended on the test tasks. This has changed in trunk (as
Adam has pointed out in the other thread). So the above should work
now with Gradle trunk.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
