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 51442] available task: Deprecated code breaks contract if folder exists
Date Tue, 28 Jun 2011 10:00:00 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51442

Stefan Bodewig <bodewig@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Stefan Bodewig <bodewig@apache.org> 2011-06-28 10:00:00 UTC ---
Properties used to be mutable in Ant before Ant 1.1 was released (eleven years
ago, I know) and not all tasks had been tidied up to honor the new immutability
rule.  One of them was <available>.

Some people already used Ant before its first release and relied on properties
being mutable - not only did they complain about the change, they also
discovered
the backdoor that was <available> and it was shared as a "workaround" among
users.

Since the Ant developers had by then become very sensitive to backwards
compatibility issues (the mutable -> immutable change did a lot to make
them, errm, us sensitive) the non-regular behavior of <available> was kept
but now created a big deprecation warning.  Many other tasks have been
changed as nobody had discovered they could be used as backdoors as well before
they were fixed.

So much for background, the usual "historical reasons".

In your case, you should wrap the available task into a <condition>
since condition will do the right thing.

-- 
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