ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31451] New: - Adapt Task to allow and check unlessCondition and ifCondition
Date Tue, 28 Sep 2004 12:23:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31451>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31451

Adapt Task to allow and check unlessCondition and ifCondition

           Summary: Adapt Task to allow and check unlessCondition and
                    ifCondition
           Product: Ant
           Version: 1.6.2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: dylan@van-iersel.org


I think it would be a very nice feature if one could use a task and have it 
check a unlessCondition and ifCondition just like targets do. This would avoid a 
lot of hassle:

  <echo message="some message" if="initialised" unless="nomessages"/>

Especially in bootstrap situations, this could come in very handy. Imagine the 
following lines defined at the project-level:

  <get src="dependency.jar" dest="lib/dependency.jar" unless="initialised"/>
  <property name="initialised" value="true"/>
  <taskdef resource="dependenttasks">
    <classpath location="lib/dependency.jar"/>
  </taskdef>

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


Mime
View raw message