ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Reilly" <>
Subject Re: Optional target support?
Date Fri, 02 Nov 2007 18:54:38 GMT
The easy way is to have a common.xml that is included in
by each subproject. The common.xml would have a "foo"
target with an empty implementation.

<target name="foo"/>

Any sub project could then have there own "foo" target that
would override the imported one.


On 11/2/07, Jeffrey E Care <> wrote:
> I've been trying to remember: is there any support for optional targets?
> The scenario is that I have a very large tree, with many (i.e. several
> hundred) subprojects; I want to run a certain target (let's call it "foo")
> on each project that defines the target, but I don't have a good way of
> knowing which projects actually define the "foo" target.
> I'm pretty sure that I could satisfy this requirement with a custom
> executor (i.e. just skip the target if it's not defined), but I was
> racking my brain to make sure that there isn't already something like this
> in 1.6.5; does anybody know?
> ____________________________________________________________________________________________
> Jeffrey E. (Jeff) Care
> IBM WebSphere Application Server
> Systems Management Tools Development
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message