Comments on: explain this

By: Woot! I crashed the javac « Just wondering….

Woot! I crashed the javac « Just wondering…. — Thu, 07 Jan 2010 18:36:15 +0000

[...] again (and again) the eclipse compiler is more robust than the sun [...]

By: Generic annoyances in java « Just wondering….

Generic annoyances in java « Just wondering…. — Thu, 07 Jan 2010 01:14:34 +0000

[...] This compiles just fine in eclipse, but once again sun’s javac is temperamental. [...]

By: Arman Sharif

Arman Sharif — Sat, 19 Jan 2008 21:09:25 +0000

I had a similar problem where I also used casting as a workaround. There’s another side to this problem though related to autoboxing.

For example, if T is an Integer, the following code will compile in eclipse but fail with javac

int result = getFoo();

The error message from javac is “type parameters of T cannot be determined; no unique maximal instance exists for type variable T with upper bounds int,java.lang.Object”

The only way to get the above code building with both is to give up autoboxing completely:

Integer result = getFoo();

This was using Eclipse 3.3.1.1 and java 5 (1.5.0_14-b03).

By: Clemens Renner

Clemens Renner — Mon, 03 Dec 2007 12:08:09 +0000

Thanks a lot for the post. It saved our day debugging the migration to Maven with a few projects.

IMHO this is just another hint at how badly generics have been implemented in Java.