ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey E Care <>
Subject Target enablement via nested conditions?
Date Thu, 23 Apr 2009 13:13:24 GMT
Off and on we've discussed more robust ways of determining target 
enablement, such as adding some type of EL syntax to if/unless.

It dawned on me yesterday that we might already have the makings of a very 
robust system: why not use conditions nested in targets to determine if 
the target is enabled? I think effectively this is what people do already 
by having the "real" target depend on a "decision" target that sets (or 
doesn't) the controlling property used in the if attribute of the real 

We can quibble on the schema, but here's an example to illustrate the 

<target name="doSomeWork">
      <istrue value="${}"/>
      <istrue value="${}"/>

  <!-- real work starts here -->



Jeffrey E. (Jeff) Care 
IBM WebSphere Application Server 
WAS Release Engineering 

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message