Jim, One other question - are you using Eclipse's Development Mode View, or did you set the USE_REMOTE_UI environment variable in your launch configuration to disable it? If you did, I think I can see why you're running into problems. We've got a bug in the plugin where we're not removing -XstartOnFirstThread when you've got this "override" set AND you're on a Mac.
Logged the following issue for this: http://code.google.com/p/google-web-toolkit/issues/detail?id=4378 Rajeev On Fri, Dec 18, 2009 at 6:12 PM, Rajeev Dayal <rda...@google.com> wrote: > Hi Jim, > > I was unable to reproduce this issue. I was using the following platform: > > Mac OS X 10.5.8 > Java 1.6.0_17 > Eclipse - Java Edition, 64 bit, Cocoa (running with Java 1.6.0_17) > > Now, here's the thing: -XstartOnFirstThread IS added the command-line, but > that is intentional; we did that so that Development Mode would not appear > as it's own application with a dock item on Mac OS X. I am not getting any > of the NSCondition-related error messages. > > In your Eclipse install, if you generate a new test app (using the New Web > App Wizard), do you run into this problem (not -XstartOnFirstThread being > present, because it should be there, but the NSLock messages appearing). > > > Rajeev > On Fri, Dec 18, 2009 at 2:40 PM, Jim Douglas <jdoug...@basis.com> wrote: > >> Hi Rajeev, >> >> Apple doesn't really give you a lot of choice about the JVM; you >> basically get what they give you. :-) >> >> The current version of Java 6 is: >> >> $ /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/ >> java -version >> java version "1.6.0_17" >> Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125) >> Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode) >> >> (Apple only distributes Java 6 on 64-bit Intel systems.) >> >> We recently moved completely to Java 6; our app no longer builds or >> runs with Java 5. >> >> This is Eclipse 3.5 Cocoa. FWIW, here's my eclipse.ini: >> >> $ cd /Applications/eclipse/Eclipse.app/Contents/MacOS >> >> $ cat eclipse.ini >> -startup >> ../../../plugins/ >> org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar >> --launcher.library >> ../../../plugins/ >> org.eclipse.equinox.launcher.cocoa.macosx_1.0.1.R35x_v20090707 >> -product >> org.eclipse.epp.package.java.product >> -showsplash >> org.eclipse.platform >> --launcher.XXMaxPermSize >> 256m >> -vmargs >> -Dosgi.requiredJavaVersion=1.5 >> -XstartOnFirstThread >> -Dorg.eclipse.swt.internal.carbon.smallFonts >> -XX:MaxPermSize=256m >> -Xms512m >> -Xmx1024m >> -Xdock:icon=../Resources/Eclipse.icns >> -XstartOnFirstThread >> -Dorg.eclipse.swt.internal.carbon.smallFonts >> >> >> On Dec 18, 11:16 am, Rajeev Dayal <rda...@google.com> wrote: >> > Hi Jim, >> > >> > A couple of questions: >> > >> > -What version of Java 6 is installed on your machine (do a java -version >> to >> > find out)? Do you experience the same problem with a different version >> of >> > Java 6 (not sure if Apple allows you to have multiple minor JDK versions >> on >> > your system at the same time), or with Java 5? >> > -Is your machine 64-bit (I think it has to be in order run Java 6 on >> > Leopard)? >> > -Are you using the Cocoa or Carbon version of Eclipse? Does the problem >> go >> > away with one versus another? >> > >> > Thanks, >> > Rajeev >> > >> > >> > >> > On Fri, Dec 18, 2009 at 11:46 AM, Rajeev Dayal <rda...@google.com> >> wrote: >> > > I'll look into this and see if I can reproduce it. >> > >> > > On Fri, Dec 18, 2009 at 9:38 AM, Jim Douglas <jdoug...@basis.com> >> wrote: >> > >> > >> Which files did you edit? >> > >> > >> On Dec 17, 11:59 am, Madprof <kickingve...@gmail.com> wrote: >> > >> > FWIW, I get the same behavior. I did a quick fix by editing >> > >> > the .launch and build.xml files so that .XstartOnFirstThread were >> > >> > suppressed. OTOH, I'm kinda freaked out by this; would like >> assurance >> > >> > that this is really a bug in the toolkit and that >> -XstartOnFirstThread >> > >> > is really supposed to work. >> > >> > >> -- >> > >> > >> You received this message because you are subscribed to the Google >> Groups >> > >> "Google Web Toolkit" group. >> > >> To post to this group, send email to >> google-web-tool...@googlegroups.com. >> > >> To unsubscribe from this group, send email to >> > >> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com><google-web-toolkit%2Bunsubs >> cr...@googlegroups.com> >> > >> . >> > >> For more options, visit this group at >> > >>http://groups.google.com/group/google-web-toolkit?hl=en. >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> >> >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
