On Jul 24, 2009, at 12:48 AM, Steve Appling wrote:
Hans Dockter wrote:
<clip>
Gradle should be able to provide such a functionality. But if we
have the build optimization implemented, would this still be an
issue for your use case?
- Hans
I don't think that the build optimization is sufficient. A few cases:
1) There are often times that a refactoring or other change may have
broken tests in a dependent project, but I am currently focused on
getting a different project's test working. I don't want the build
tool to force me to fix the dependent project's tests just so I can
compile the one I am focused on.
Right.
2) I don't want someone else's change that somehow made it into the
VCS keep me from doing my work. Even if their change broke a unit
test in a dependent project, it may not impact what I am doing now,
so it shouldn't keep me from building.
Right.
3) We would like our Continuous Integration server to be able to do
a clean build of the whole system, but only run tests for a single
project.
OK
Thanks for the use cases. They are convincing :)
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
