On Fri, Apr 8, 2011 at 11:26 AM, Jörg Schaible <joerg.schai...@scalaris.com> wrote:
>>> DISCOVERY-6: release 0.5 is targeted for Java5, I don't know if this >>> issue is still valid - I mean, if there are Java5 implementations >>> where ClassLoader.getResource() is not supported... I googled a little >>> and didn't find anything useful, I'm tempted to resolve it with a >>> "Won't fix" but I'm sure anyone here can tell me more. >> >> If ClassLoader.getResource() is unsupported then almost everything >> will break. I doubt the validity. And in that case, it would be a JVM >> bug and not a discovery bug. WONTFIX sounds sensible. > > You cannot blame necessarily the JVM for a custom classloader. Why not > simply use Emmanuel's suggestion? Sorry for misunderstanding that. I though that "Java5 implementations" meant a JVM classloader. Fix my words to say "it would be a classloader bug", but the result stays the same. Jochen > >>> DISCOVERY-7: I'd postpone, 0.5 was initially in my mind a maintenance >>> release, I wouldn't add any new behavior not supported before... WDYT? >> >> I'd close this as WONTFIX as well with the note that the user should >> indeed have used '$' as a separator for inner classes. > > +1 > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- I Am What I Am And That's All What I Yam (Popeye) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
