Thanks Ben. I'll correct the first post. On Thu, Oct 15, 2009 at 11:04 AM, Ben <[email protected]> wrote:
> > Hi, Miguel, I already did that and I think maybe the instructions in > the first post of this thread should do some changes otherwise it is > going to confuse people. > > Thanks a lot! 1.1.2 is a timely update for gwt 2.0 > > -Ben > > On Oct 15, 6:39 am, Miguel Méndez <[email protected]> wrote: > > On Wed, Oct 14, 2009 at 2:47 PM, Ben <[email protected]> wrote: > > > > > Okay, just checked the command line. It looks like it still appends - > > > XstartOnFirstThread: > > > > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/ > > > java -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost: > > > 57735 -Xmx512m -XstartOnFirstThread -Dfile.encoding=UTF-8 -classpath / > > > Users/bhu/workspace35/GWT2/src:/Users/bhu/workspace35/GWT2/war/WEB-INF/ > > > classes:/Users/bhu/Downloads/gwt-2.0.0-ms1/gwt-user.jar:/Users/bhu/ > > > Downloads/gwt-2.0.0-ms1/gwt-dev-mac.jar com.google.gwt.dev.HostedMode - > > > startupUrl GWT2.html -war /Users/bhu/workspace35/GWT2/war -logLevel > > > INFO -style OBFUSCATED -port 8080 com.test.gwt.GWT2 > > > > > I am using the GWT 2 Milestone 1 release, I just created the sample > > > project using GWT2.0 and launch it. I tried to include App Engine, it > > > is the same thing. I upgraded Google Plugin from 1.1.1 to 1.1.2 this > > > morning. > > > > I see that the command line has a gwt-dev-mac.jar on the classpath, but > MS1 > > did not include a gwt-dev-mac.jar. Did you use the symlink trick to get > the > > plugin to work with MS1 (symlink gwt-dev-mac.jar to gwt-dev.jar)? If so > you > > will want to remove the symlink and then it should work. > > > > Please let me know. > > > > > > > > > On Oct 14, 1:54 pm, Miguel Méndez <[email protected]> wrote: > > > > 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.h. > > > .. > > > > > . > > > > > > > > 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... > > > > 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 -~----------~----~----~----~------~----~------~--~---
