ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conor MacNeill <>
Subject Re: Do we want to break BWC in AntClassLoader$ResourceEnumeration? (was Re: DO NOT REPLY [Bug 51579] ...)
Date Sat, 06 Aug 2011 17:11:49 GMT
On Sun, Aug 7, 2011 at 02:43, Stefan Bodewig <> wrote:
> On 2011-07-29, <> wrote:
> The Enumeration returned by AntClassloader#getResources violates the
> Enumeration contract in that getNextElement() returns null rather than
> throwing a NoSuchElementException when the enumeration is exhausted.  It
> has done so for ten years now.
> Do we want to make it adhere to the contract or does anybody feel this
> is too dangerous?

I think it should probably be fixed. In typical usage, the
hasMoreElements call would protect callers from encountering the
problem so it's not that dangerous to make it comply with the API. The
BWC break is relatively minor, IMHO.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message