Fortunately (?), Apple hasn't put Java 6 on my computer yet. :-)
On Dec 28, 2007 1:59 PM, Kevin Menard <kmenar..ervprise.com> wrote:
> .. . . is likely going to be a pipedream.
>
> It appears Sun went out of their way to make the interface changes
> incompatible between Java 5 & Java 6. Not only do the interface changes add
> new methods, but these new methods use new types. So, throwing runtime
> exceptions isn't an option because the types aren't available to a Java 5
> compiler. Not implementing a methods won't work in a Java 6 compiler
> because the interface isn't fully implemented at that point. So, we have a
> software engineering 101 principle violated.
>
> Fortunately, a Cayenne JAR built in Java 5 works fine in Java 6. Anyone
> that wants to build the code in Java 6 is going to have problems though.
> Oh, and just to make matters worse, the Windows Java 6 installer throws its
> executables into %System32% so they get found on the path first. So, not
> only do you have to make Java 5 your JAVA_HOME (in order for mvn to work),
> but you also have to blow out those binaries in order for the correct javac
> to be used in general.
>
> Lots of fun. Thank you, Sun.
>
> --
> Kevin
>
>
This archive was generated by hypermail 2.0.0 : Fri Dec 28 2007 - 14:10:59 EST