That's what I was thinking too. Not a problem, and I really appreciate your testing and followup on this. It's no problem for me to continue to start devmode from the command line for now.
On Dec 21, 7:51 am, Rajeev Dayal <[email protected]> wrote: > Hey Jim, > > Based on your comments in the bug report, it looks like the fact that your > app uses Swing is what causes the problem. In that case, > -XstartOnFirstThread should not be present. Unfortunately, due to the way > that the Web Application Launch Configurations work, there is no way to > disable this argument from being added automatically (on the Mac). > > We're thinking of making some changes to the launch configurations in the > near future that will make this option configurable (along with others) > instead of fixed. For now, your best workaround would be to use a Java > launch configuration (as you've been doing). > > Rajeev > > On Fri, Dec 18, 2009 at 6:36 PM, Jim Douglas <[email protected]> wrote: > > > -XstartOnFirstThread IS added the command-line, but that is intentional > > > Ahh, that's useful information! Would it be possible to make that a > > configurable option? > > > I just generated the trivial "Web Application Starter Project", and it > > runs without generating those error messages. But I'm not sure what > > specifically in my app is triggering those errors -- just that they go > > away when I run DevMode without the -XstartOnFirstThread flag. > > > Jim. > > > On Dec 18, 3:12 pm, Rajeev Dayal <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> > > > > wrote: > > > > > > I'll look into this and see if I can reproduce it. > > > > > > > On Fri, Dec 18, 2009 at 9:38 AM, Jim Douglas <[email protected]> > > > > wrote: > > > > > > >> Which files did you edit? > > > > > > >> On Dec 17, 11:59 am, Madprof <[email protected]> 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 > > > > [email protected]. > > > > > >> To unsubscribe from this group, send email to > > > > > >> [email protected]<google-web-toolkit%[email protected]><google-web-toolkit%2Bunsubs > > [email protected]><google-web-toolkit%2Bunsubs > > > > [email protected]> > > > > > >> . > > > > > >> 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 > > [email protected]. > > > > To unsubscribe from this group, send email to > > > > [email protected]<google-web-toolkit%[email protected]><google-web-toolkit%2Bunsubs > > [email protected]> > > > > . > > > > 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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%[email protected]> > > . > > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
