ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <nicolas.lale...@hibnet.org>
Subject Re: Naming of target-group
Date Fri, 18 Dec 2009 19:56:56 GMT
On Fri, 18 Dec 2009 16:12:25 +0100, Stefan Bodewig <bodewig@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 good
> anyway.
> 
> 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?
> 
>     (a) target-group

no objection for me

> 
>     (b) phase
> 
>     (c) goal

Both I would prefer not to, as this could recall maven concepts which are
not quite similar to the target-group current implementation.

>     (d - z) anything else

abstract-target, so it says it is about making some "API" in the build
script.

> 
> (2) What do we want to call the attribute of <target> that is used to
>     add a target to a depends-list of (1)?
> 
>     (a) group

fine for me with the target-group element

> 
>     (b - z) anything else

an attribute corresponding to abstract-target: hookedto. A first idea
would be "implements", but it doesn't feel like inheritance. I prefer the
"hook" notion that the target will be added to the dependency of another
abstract one.

Nicolas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message