Hi all
I've been responsible for too many bad naming choices to try to come up
with something new here. I've collected the names that I recall being
proposed, but I may have missed some and the choices may not be good
anyway.
I understand that (2) is very dependent on (1).
(1) What do we want
When I first seriously thought about volunteering as 1.8.0 release
manager it was late this summer and I thought I'd write a mail like this
in September. Life interfered and there've been way more changes in
trunk than I initially thought, so now its almost christmas.
What I'd like to propose is
I understand that (2) is very dependent on (1).
(1) What do we want to call the new element that behaves quite a bit
like a target but has a dependency list that can be extended?
- moving-target (very familiar for people working in IT)
or
- mutable-target ?
(a) target-group
(b)
Stefan Bodewig wrote:
Hi all
I've been responsible for too many bad naming choices to try to come up
with something new here. I've collected the names that I recall being
proposed, but I may have missed some and the choices may not be good
anyway.
I understand that (2) is very dependent on
I have to say, I think goal is semantically reasonable--that said I
would want to use it. Let's just say I'd like to emphasize the
dissimiliarities between Ant and Maven. ;) phase is not terrible,
but seems to imply that a buildfile represents a single story which
is not always the
On 2009-12-18, Kevin Jackson foamd...@gmail.com wrote:
I understand that (2) is very dependent on (1).
(1) What do we want to call the new element that behaves quite a bit
like a target but has a dependency list that can be extended?
- moving-target (very familiar for people working in
On Fri, 18 Dec 2009 16:12:25 +0100, Stefan Bodewig bode...@apache.org
wrote:
Hi all
I've been responsible for too many bad naming choices to try to come up
with something new here. I've collected the names that I recall being
proposed, but I may have missed some and the choices may not be
