ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Czernuszka" <george.czernus...@nscgroup.co.uk>
Subject RE: refid still not behaving as expected in 1.7.0
Date Thu, 30 Aug 2007 11:23:25 GMT

Does this mean that bug 36955 should be re-opened, or a new bug created?


> -----Original Message-----
> From: Peter Reilly [mailto:peter.kitt.reilly@gmail.com] 
> Sent: 30 August 2007 10:35
> To: Ant Users List
> Subject: Re: refid still not behaving as expected in 1.7.0
> 
> The behavior as described in the WHATSNEW is what was 
> initially was done. However this broke too many builds - with 
> references to out-of-band ids. So the code was modified to 
> store all the out-of-band ids and if the reference could not 
> be found, to look up that and if found to use that reference 
> and to output a long message.
> 
> In ant 1.8.0, this out-of-band resolution will probably be 
> removed. One could change the <isreference> implementation to 
> report false for out-of-band references, but I do not think 
> that is a good idea.
> 
> Peter
> 
> > > One of the significant changes in 1.7.0 was, apparently:
> > >
> > > " * Defer reference process. Bugzilla 36955, 34458, 37688.
> > > However, my version of ANT 1.7.0 (binary download) seems 
> to behave in the 'old' way. I have looked in WHATSNEW under 
> SVN, and can see no suggestion that there was a problem. So, 
> my question, how can I get 'isreference' to "properly" 
> identify whether a path, for example, has been set at the 
> point where the condition is tested.
> > >


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


Mime
View raw message