ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46780] <target>'s condition check is wrong
Date Thu, 05 Mar 2009 04:07:18 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46780


Stefan Bodewig <bodewig@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID




--- Comment #4 from Stefan Bodewig <bodewig@apache.org>  2009-03-04 20:07:16 PST ---
Well, "this behavior has been intact in Ant for many years" *does* make it
right since it is the behavior that many many build files rely on.

something like

<target name="check-property">
  <condition that may set property X .../>
</target>

<target name="do-something-if-X" if="X" depends="check-property">
  ...
</target>

<target name="do-something-unless-X" unless="X" depends="check-property">
  ...
</target>

<target name="do-something" depends="do-something-if-X,do-something-unless-X"/>

is a very common pattern which would be broken if we changed the behavior.

I know that other tools have taken a different approach (NAnt is one such
example, they use if/unless exactly the way you'd prefer it to work), but Ant's
behavior is known, documented and has been a conscious choice.

http://ant.apache.org/faq.html#stop-dependency

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message