[MatthewC529]

Isn't this discouraged because the JVM itself is not the standard HotSpot JVM build for 1.5? It is the Squawk VM that runs the CLDC 1.1 (1.2?) implementation? I mean the whole reason is that in many cases you are having fun balancing memory when you want to write larger implementations. Hence CLDC, the cRIO is quite often very hard pressed for memory.

Not to say it is impossible for the cRIO to handle Generics, Autoboxing and Lists but I had always thought the reason for this was the cost of what is already implemented in the FRC SDK and the fact that Squawk VM does not have the same capabilities as HotSpot but with a smaller memory footprint.

It has been a simple task with Ant to change its build.xml but if this is fine, what prevents me from moving on to higher Java ME versions?

I am curious, really, if you have tried running that code at all on a robot in a meaningful way, because I feel this would be incompatible with the Squawk VM. But I assume you havent since you said you ARE switching.