Sometimes I get a little sloppy and forget to run a clean maven build before I check in.
There's some decided differences between the Eclipse compiler and the Sun JDK compiler when it comes to generics. From what I can tell, Eclipse is wrong but it feels so right :-) Seriously, Generics is a crock of shit. I did finally realize why Generics are so god awful complicated ... if you did the right and simple thing (let the compiler introduce the necessary cast) that would work most of the time, but it would make selecting the correct method difficult when you have method overloading (lots of methods with the same name but different parameters). Java really wants to be able to determine that at compile time, and with you start pulling out real typing, it becomes a runtime decision. On 1/10/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 1/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: hlship > Date: Wed Jan 10 14:28:35 2007 > New Revision: 495012 [..] > > - Set<Class> classes = CollectionFactory.newSet(Arrays.asList( > - String.class, > - Map.class, > - List.class)); > + List classes = Arrays.asList(String.class, List.class, Map.class); > > replay(); > Ah... Howard! I start to hate you ;) ...sorry for the noise in my previous post. Now compile pass even on maven. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
