On Sun, 24 Sep 2006 14:32:56 -0500, Mike Grundvig wrote: > I know it's considered "evil" but in cases like this, it just makes sense.
You're blaming the wrong party. > Why isn't the backport jar just using the same package names as the 1.5 > concurrent code? If that were being done, you would simply have that jar The answer is simply "because that's not possible". You cannot use the java.* namespace for custom classes, otherwise some crackhead could sneak a custom java.lang.Object on the classpath and steal your security. (that's just one example. there are numerous other reasons.) > on the classpath if you were in 1.4 and remove it for 1.5. Piece of cake, > 100% compatibility and it's much simpler for all involved. No more > backport jar even if you are using 1.5. Yes, and broken serialization too! -h
