Committed.
Steve Loughran wrote:
the only thing I see this breaking is any class which has a java5 enum
of a specific name, and a legacy enum with the same name.
You can't; enums and classes use the same namespace. Or maybe I'm
missing your point.
you end up writing tasks that are java5+ only, of course.
Of course. But this is hardly a concern if the task is for your own use
and your project uses Java 5+ anyway.
-J.
--
[EMAIL PROTECTED] x22801 netbeans.org ant.apache.org
http://google.com/search?q=e%5E%28pi*i%29%2B1
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
