Sunday, January 16, 2005

So much for Eclipse 3.1 Compliance

As an experiment, I imported the current code base for Thinking in Java 4e into the latest Eclipse 3.1 beta, since everyone has been saying how very compliant it is to J2SE5. After fooling around a bit to get rid of classpath and package import issues, my code base, which builds without problem, reported 1021 errors in Eclipse. A lot of these errors came from other errors, and one of the show-stopper starting errors is this one:

The type List is not generic;
it cannot be parameterized with arguments <Character>

For the perfectly legitimate line:

List<Character> chars = new ArrayList<Character>();

It accepts the code if I change the line to:

ArrayList<Character> chars = new ArrayList<Character>();

I think it's safe to say that, with a bug that fundamental, it's going to be awhile before Eclipse 3.1 is J2SE5 compliant.

Too bad; the other parts of it looked promising.