Strange. I just tried it on my Eclipse 3.5 carbon & cocoa 64 bit and both work correctly. Are you sure that you have the 1.1.2 plugin? Are you using GWT & App Engine or just GWT? It would help to get see the command line used to by the launch configuration. Lastly, are you using a Contributor SDK<http://code.google.com/eclipse/docs/gwt_contrib_sdks.html>? (If you are you'll need to a clean followed by a build).
On Wed, Oct 14, 2009 at 12:27 PM, Ben <[email protected]> wrote: > > I have just installed 1.1.2 in my Eclipse 3.5. Created a new sample > project using plugin with newest GWT 2 MS1. Then launch the > application, it still throws out error msg like this: > > 2009-10-14 12:16:42.869 java[8409:80f] [Java CocoaComponent > compatibility mode]: Enabled > 2009-10-14 12:16:42.871 java[8409:80f] [Java CocoaComponent > compatibility mode]: Setting timeout for SWT to 0.100000 > 2009-10-14 12:16:43.770 java[8409:17f03] *** -[NSConditionLock > unlock]: lock (<NSConditionLock: 0x114840> '(null)') unlocked when not > locked > 2009-10-14 12:16:43.770 java[8409:17f03] *** Break on _NSLockError() > to debug. > 2009-10-14 12:16:43.901 java[8409:17f03] *** -[NSConditionLock > unlock]: lock (<NSConditionLock: 0x19c3d0> '(null)') unlocked when not > locked > 2009-10-14 12:16:43.902 java[8409:17f03] *** Break on _NSLockError() > to debug. > 2009-10-14 12:16:44.014 java[8409:17f03] *** -[NSConditionLock > unlock]: lock (<NSConditionLock: 0x19bfb0> '(null)') unlocked when not > locked > 2009-10-14 12:16:44.015 java[8409:17f03] *** Break on _NSLockError() > to debug. > 2009-10-14 12:16:44.133 java[8409:17f03] *** -[NSConditionLock > unlock]: lock (<NSConditionLock: 0x13a4d0> '(null)') unlocked when not > locked > 2009-10-14 12:16:44.134 java[8409:17f03] *** Break on _NSLockError() > to debug. > > The development shell does get launched, but it is clickable. Whenever > I move my mouse over the development shell, it keeps loading so it is > basically not usable. > > BTW, I am using Eclipse 3.5 Cocoa 64bit version on Leopard. Is this > the problem? > > Thanks, > Ben > > On Oct 13, 6:34 am, Miguel Méndez <[email protected]> wrote: > > Barring any last minute issues, we should have version 1.1.2 of the > plugin > > ready to go by end of day today. It will be compatible with MS1 and it > will > > also address this -XstartOnFirstThread issue which causes the beach ball. > > Please see issuehttp:// > code.google.com/p/google-web-toolkit/issues/detail?id=3923for more > > details. > > In the meantime, you could create a java launch configuration in Eclipse > and > > specify the entry point, GWT arguments and tweak the classpath. The > > following links should help get you setup: > http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.html,http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM > . > > > > HTH, > > > > > > > > On Tue, Oct 13, 2009 at 12:02 AM, miller <[email protected]> > wrote: > > > > > I am using Snow Leopard w/ Eclipse Plugin. When I run in Development > > > mode, my development mode window is under constant beach ball. > > > > > How do you work around this issue? are there directions anywhere? > > > > > thanks- > > > Mike > > > > > On Oct 9, 5:36 pm, Ben <[email protected]> wrote: > > > > Hey, Guys, > > > > > > Thanks for the reply. I just found out that it is an open bug for > > > > OOPHM on Mac OS X. If you are curious, the bug is here: > > >http://code.google.com/p/google-web-toolkit/issues/detail?id=3923. > > > > > > cheers > > > > Ben > > > > > > On Oct 9, 2:01 pm, Christian Goudreau <[email protected]> > > > > wrote: > > > > > > > I did the same trick as Sky to get my project to work. But I still > have > > > to > > > > > problems. > > > > > > > First : When I lauch it in development mode, I can't close the > > > development > > > > > mode hosted window without closing eclipse, that's anoying because > I > > > can't > > > > > switch to debug mode... So now, I just run it in debug without > brake > > > point > > > > > to make sure I'm able to stop it and close the development mode > hosted > > > > > window. > > > > > > > Second : I have the new project html files instead of the one I'm > using > > > with > > > > > my project ! That's really weird, because on top of my application > I > > > have > > > > > everything from the new project html file, but my JS files, css > files > > > ar > > > > > linked correctly ! LOL > > > > > > > Christian > > > > > > > On Fri, Oct 9, 2009 at 1:36 PM, Ben <[email protected]> wrote: > > > > > > > > Sky, thanks for you reply. I am using Eclipse 3.5.0 (I am not > sure > > > > > > updating to 3.5.1 matters) and my google eclipse plugin is > > > uptodate.It > > > > > > still throws that exception if I just use default google plugin > > > launch > > > > > > configuration. > > > > > > > > On Oct 8, 5:39 pm, Sky <[email protected]> wrote: > > > > > > > Ben, with 2.0 my projects launch the development shell when > using > > > the > > > > > > > Google plugin launch options. It launched for me even when I > just > > > > > > > changed a project from 1.7.1 to 2.0, but you could try creating > a > > > > > > > whole new project with 2.0 from the start and copy the files > over > > > from > > > > > > > the old project. > > > > > > > > > Make sure the google plugin and the appengine is fully up to > date. > > > > > > > What version of Ecipse are you using? Try downloading the new > 3.5.1 > > > > > > > version. > > > > > > > > > Sorry I can't help any more than that. gl > > > > > > > > > On Oct 8, 3:50 pm, Ben <[email protected]> wrote: > > > > > > > > > > I have noticed that if you use Google Plugin to launch your > > > project > > > > > > > > with 2.0 jar. The development shell does not launch at all. > You > > > have > > > > > > > > to launch it as a Java Application and set up some parameters > by > > > > > > > > yourself, then you are able to see that GWT Develop Mode > popup > > > shell > > > > > > > > window. Is my observation correct? > > > > > > > > > > On Oct 8, 1:33 pm, Sky <[email protected]> wrote: > > > > > > > > > > > I got debugging to work! > > > > > > > > > > > I created a new GWT web app with the Eclipse google plugin > > > using GWT > > > > > > > > > 2.0MS1 as the SDK. This is what most likely solved my > problem. > > > Simply > > > > > > > > > changing a project from GWT 1.7.1 to 2.0 must not be making > all > > > the > > > > > > > > > necessary changes to the auto generated files to be > properly > > > > > > > > > compatible. Obviously this sort of thing will be ironed out > for > > > > > > > > > release. > > > > > > > > > > > Then I needed to first launch (not a debug launch) the > newly > > > created > > > > > > > > > GWT web app (with the default app still intact). I tried > this > > > with a > > > > > > > > > browser that did not have the plugin installed (FF3.5) and > when > > > > > > > > > navigating to the URL it auto directed me to the plugin > install > > > web > > > > > > > > > page and after installing the plugin the web app was > rendered > > > > > > > > > correctly. Note that at this point I have not compiled the > app > > > so the > > > > > > > > > plugin is indeed doing its job! The java code is what is > > > interacting > > > > > > > > > synchronously with the browser instead of the compiled JS! > > > > > > > > > > > Note that I had first attempted to launch the app in debug > mode > > > which > > > > > > > > > gave me 3 errors related to the Appengine > > > > > > > > > (com.google.apphosting.utils.jetty... yet eclipse could not > > > resolve > > > > > > > > > com.google.apphosting.utils.jetty) but those errors went > away > > > as soon > > > > > > > > > as I did a non debug launch. In other words, the app was > able > > > to do a > > > > > > > > > debug launch only after doing a regular launch. > > > > > > > > > > > With the debug launch successful I was able to hit a > breakpoint > > > in > > > > > > the > > > > > > > > > onModuleLoad method of this default web app! I then copied > all > > > the > > > > > > > > > required files from my previous project into this new one. > Once > > > again > > > > > > > > > I was able to hit a breakpoint on the onModuleLoad method! > > > > > > > > > > > I am very excited to have this working! > > > > > > > > > > > On Oct 7, 8:32 pm, Sky <[email protected]> > wrote: > > > > > > > > > > > > I set GWT 2.0 as the SDK for my project and it changed to > the > > > new > > > > > > > > > > Development Swing UI In-browser mode instead of the old > > > hosted > > > > > > mode. I > > > > > > > > > > placed the given URL in both FF3.5 and IE8 and neither > auto > > > > > > installed > > > > > > > > > > the required plugin. Since my app is already compiled it > > > renders > > > > > > fine > > > > > > > > > > but I cannot debug. I tried manually installing the > correct > > > plugins > > > > > > > > > > fromhttp:// > > > code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > > > > > > > > > > the server is either only serving the compiled files or > > > something > > > > > > is > > > > > > > > > > wrong with the plugin because I cannot debug; breakpoints > are > > > not > > > > > > hit. > > > > > > > > > > > > Does anyone know what I am doing wrong? > > > > > > > > > > > > On Oct 7, 11:37 am, Joseph Arceneaux < > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > May we presume that the Snow Leopard issue is now > history? > > > > > > > > > > > Thanks, > > > > > > > > > > > Joe > > > > > > > > > > > > > On Mon, Oct 5, 2009 at 4:43 PM, Amit Manjhi < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > We are excited to release the first milestone build > for > > > GWT 2.0 > > > > > > today. > > > > > > > > > > > > This milestone provides early access (read: known to > > > still be > > > > > > > > > > > > unfinished and buggy) to the various bits of core > > > functionality > > > > > > that > > > > > > > > > > > > will be coming in GWT 2.0. Please download the bits > from: > > > > >http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=2.. > .. > > > > > > > > > > > > > > Things that are changing with GWT 2.0 that might > > > otherwise be > > > > > > > > > > > > confusing without explanation > > > > > > > > > > > > * Terminology changes: We're going to start using the > > > term > > > > > > > > > > > > "development mode" rather than the old term "hosted > > > mode." The > > > > > > term > > > > > > > > > > > > "hosted mode" was sometimes confusing to people, so > we'll > > > be > > > > > > using the > > > > > > > > > > > > more descriptive term from now on. For similar > reasons, > > > we'll > > > > > > be using > > > > > > > > > > > > the term "production mode" rather than "web mode" > when > > > > > > referring to > > > > > > > > > > > > compiled script. > > > > > > > > > > > > > > * Changes to the distribution: Note that there's only > one > > > > > > download, > > > > > > > > > > > > and it's no longer platform-specific. You download > the > > > same zip > > > > > > file > > > > > > > > > > > > for every development platform. This is made possible > by > > > the > > > > > > new > > > > > > > > > > > > plugin approach used to implement development mode > (see > > > below). > > > > > > The > > > > > > > > > > > > distribution file does not include the browser > plugins > > > > > > themselves; > > > > > > > > > > > > those are downloaded separately the first time you > use > > > > > > development > > > > > > > > > > > > mode in a browser that doesn't have the plugin > installed. > > > > > > > > > > > > > > Functionality that will be coming in GWT 2.0 > > > > > > > > > > > > * In-Browser Development Mode: Prior to 2.0, GWT > hosted > > > mode > > > > > > provided > > > > > > > > > > > > a special-purpose "hosted browser" to debug your GWT > > > code. In > > > > > > 2.0, the > > > > > > > > > > > > web page being debugged is viewed within a > regular-old > > > browser. > > > > > > > > > > > > Development mode is supported through the use of a > > > native-code > > > > > > plugin > > > > > > > > > > > > for each browser. In other words, you can use > development > > > mode > > > > > > > > > > > > directly from Safari, Firefox, IE, and Chrome. > > > > > > > > > > > > > > * Code Splitting: Developer-guided code splitting > allows > > > you to > > > > > > chunk > > > > > > > > > > > > your GWT code into multiple fragments for faster > startup. > > > > > > Imagine > > > > > > > > > > > > having to download a whole movie before being able to > > > watch it. > > > > > > Well, > > > > > > > > > > > > that's what you have to do with most Ajax apps these > days > > > -- > > > > > > download > > > > > > > > > > > > the whole thing before using it. With code splitting, > you > > > can > > > > > > arrange... > > > > read more » > > > -- Miguel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
