Steve Appling wrote:
Hans Dockter wrote:
<clip>
What I like with the lifecycle approach is that it introduces a
concept we are talking about a lot. This looks like a good thing. At
the moment is it just designed as an aggregating task but that might
evolve in the future. We might be able to combine it with synthetic
tasks.
1a) gradle test
1b) gradle build
2) gradle buildSingle
3a) gradle clean test
3b) gradle clean build
4.) gradle buildDependents
- Hans
I have implemented this approach, but would like to haggle about the
names some.
Let's just talk about the 3 forms of "build".
A) Just this project
B) This project and the projects it depends on in the testRuntime
configuration
C) This project and projects that depend on it in their testRuntime
configuration.
I think Hans' suggestion above was:
A) buildSingle
B) build
C) buildDependents
I think that the one of these that I will use the most is actually A, so
I would prefer it to be just plain "build". I also think that the
direction of "dependent" is frequently confusing for people. It is
often used incorrectly in the reverse direction. I would like any other
suggestions for names for the three build tasks. Currently I have
implemented:
A) build
B) buildUses
C) buildUsed
I don't particularly like these names either, though. Any other
suggestions?
I think I am settling on:
A) build
B) buildNeeded
C) buildDependents
I'll check it in like this if I don't hear any better ideas today. We can
change it whenever someone comes up with something better.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
