ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject target-group in trunk
Date Thu, 10 Dec 2009 05:11:34 GMT

this is just a description of what target-group in trunk currently is
and what it is not.  I'll describe the implementation rather than the
initial phase concept as it is implemented in EasyAnt which uses a
custom ProjectHelper to implement its slightly different concept.

This mail serves as background in addition to the thread Nicolas has

A target-group is basically a target with two differences:

* must be empty

* its depends list can be added to during parse time.  Other targets and
  target-groups can declare themselves as part of the group and get
  added to the group's depends list.

That's all.  Order of execution is still only determined by the depends
attributes of all targets.

For anybody running a build target-groups are just like targets.  They
are listed together with targets in -projecthelp and create BuildEvents
and log output of targets.

A target-group is not a container of targets.  It doesn't provide a
grouping in a sense that a target would be executed as part of a group -
the depends lists of all targets and target-groups still determine the

Since a target-group is always empty, the if and unless attributes don't
have any effect at all.

Of course we could change the implementation to get to a more
composite-like implementation - making if and unless useful and maybe
introduce new build events - it is just not clear (to me) whether the
additional effort would provide anything more useful.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message