Ultimately, I think it would be nice if the entire API were parameterized appropriately. I don't see much benefit in blocking work until that occurs though. So, it may be worthwhile to just disable the warning in your workspace for now and chip away at things over time.
On 11/19/07 10:31 AM, "Michael Gentry" <[EMAIL PROTECTED]> wrote: > I apologize if this has been talked about before (I don't recall > seeing it), but are we going to worry about Java 5/Eclipse warnings > such as "ArrayList is a raw type. References to generic type > ArrayList<E> should be parameterized" initially? I just did a fresh > update (yes, I need to do it at home, too, so I can work on stuff) and > these types of warnings are all over the place (at least in my Eclipse > environment). > > Just curious what everyone things here ... > > Thanks, > > /dev/mrg >> -- Kevin Menard Servprise International, Inc. Remote reboot & power control for network equipment www.servprise.com +1 508.892.3823 x308
