Ahh - gotcha. Wouldn't this be a backwards compatability issue with the JDK? I thought Sun took those seriously (or is that only for the JVM itself)?
Also as an aside, for some reason update-alternatives for javac was insufficient. I have a feeling that ant looks at the java that it was run with to find the path to javac instead of looking at the javac on the path, so I also had to do an update-alternatives for java. On Fri, Mar 13, 2009 at 3:58 AM, John Tamplin <[email protected]> wrote: > On Fri, Mar 13, 2009 at 3:53 AM, Vitali Lovich <[email protected]> wrote: > >> Don't feel like you need to do this workaround just because I said I was >> using OpenJDK - that's just the default install. I have no qualms about >> installing Sun's version (it's just an apt-get away and I'm not a GPL >> purist). > > > The problem is that the same code is making its way into Sun's 1.7 JDK, so > if they don't fix the bug we will have to add the workaround to keep it > possible to build with the latest JDK. > > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
