The latest GWT 1.5 is out. Please download it, give it a try, and then erase your other pre-release versions of GWT so you won't get confused. The version that was released as 'final' has the version number 1.5.2
On Sat, Aug 30, 2008 at 3:40 AM, Agnes <[EMAIL PROTECTED]> wrote: > > I will be more specific, I am trying to do it for all the files, but I > am more interested in gwt-maps.jar. > The error I get is : > Compiling 212 source files to dir. > ~Polygon.java: 20 cannot find symbol > symbol: Class JsArray > location: package com.google.gwt.core.client > import com.google.gwt.core.client.JsArray; > > and the list goes on > basically it cannot find symbol, > symbol: class JsArray > SO the end result > Build FAILED. > > > > On 25 ago, 23:37, "Eric Ayers" <[EMAIL PROTECTED]> wrote: >> Hi Evan, >> >> JsArray is a part of 1.5 RC2 >> >> >> >> >> >> On Mon, Aug 25, 2008 at 5:35 PM, Evan Ruff <[EMAIL PROTECTED]> wrote: >> >> > Eric, I think I must be getting some version conflicts, maybe? >> >> > I've got GWT_HOME pointing to gwt-windows-1.5.0 installation >> > directory, which is what I use in my project. >> > I've got GWT_TOOLS pointing to the gwt tools SVN repository srcs that >> > you pointed me to above. >> >> > When I do a plain ant, it looks like it's going to rock it through, >> > but then it gives me several errors in gears, starting with: >> > [gwt.javac] E:\Development Projects\Google API for GWT\gears\gears\src >> > \com\google\gwt\gears\client\impl\Utils.java:20: cannot find symbol >> > [gwt.javac] symbol : class JsArrayString >> > [gwt.javac] location: package com.google.gwt.core.client >> > [gwt.javac] import com.google.gwt.core.client.JsArrayString; >> >> > And when I hit an 'ant maps', it looks good for a while then bombs out >> > with with: >> > [gwt.javac] E:\Development Projects\Google API for GWT\maps\maps\src >> > \com\google\gwt\maps\client\overlay\Polygon.java:102: cannot find >> > symbol >> > [gwt.javac] symbol : class JsArray >> > [gwt.javac] location: class com.google.gwt.maps.client.overlay.Polygon >> > [gwt.javac] private static native JsArray<EncodedPolyline> >> > nativeArrayToJavaScriptObject( >> >> > So it looks like I might have a versioning issue? Both were just >> > downloaded today from SVN, so maybe this really won't compile against >> > my GWT version? >> >> > Thanks for all your help! I appreciate you taking a look at the >> > issues! >> >> > E >> >> > On Aug 25, 3:14 pm, "Eric Ayers" <[EMAIL PROTECTED]> wrote: >> >> Yup, sorry I left out that step. >> >> >> Checkout thehttp://google-web-toolkit.googlecode.com/svn/toolsand >> >> set GWT_TOOLS to the directory where you place it. >> >> GWT_HOME should point to an unpacked distribution of gwt-1.5.1 (1.5 RC2). >> >> >> -Eric. >> >> >> On Mon, Aug 25, 2008 at 3:01 PM, Evan Ruff <[EMAIL PROTECTED]> wrote: >> >> >> > Hey Eric, >> >> >> > I gave this a shot earlier today and ended up having a whole host of >> >> > weird errors. My first question is, will the trunk run against RC1 or >> >> > will I have to upgrade to RC2? >> >> >> > GWT_HOME referes to my GWT installation, I assume, but where does >> >> > GWT_TOOLS point too? >> >> >> > And finally, when I do run ant, I get some errors starting with : >> >> >> > [taskdef] Could not load definitions from resource net/sf/antcontrib/ >> >> > antlib.xml. It could not be found. >> >> >> > and things like: >> >> >> > [gwt.javac] Compiling 2 source files to E:\Development Projects\Google >> >> > API for GWT\gadgets\build\out\build-tools\customchecks\bin >> >> > [gwt.javac] E:\Development Projects\Google API for GWT\gadgets\build- >> >> > tools\customchecks\src\com\google\gwt\checkstyle\FieldCheck.java:19: >> >> > package com.puppycrawl.tools.checkstyle.api does not exist >> >> > [gwt.javac] import com.puppycrawl.tools.checkstyle.api.DetailAST; >> >> >> > Is this because of a bad GWT_TOOLS enviorment var? >> >> >> > Thanks for your help! >> >> >> > Evan >> >> >> > On Aug 25, 2:43 pm, "Eric Ayers" <[EMAIL PROTECTED]> wrote: >> >> >> I've seen similar stack traces fail when the Maps API is not really >> >> >> loaded. More recent versions of the gwt-maps library detect this and >> >> >> display a message. It could also be a problem similar to that >> >> >> described in issue 112 that was windows specific and not fixed until >> >> >> r296. >> >> >> >> building your own jar from the latest source isn't too hard. You will >> >> >> need the 1.5 or 1.6 version of the JDK, the Ant utility and the >> >> >>Subversionclient. Download thesubversioncode using 'svn >> >> >>cohttp://gwt-google-apis.googlecode.com/svn/trunktrunk', then >> >> >> run 'ant' on the top level file. The gwt-maps library will build and >> >> >> end up under maps/build/lib/gwt-maps.jar >> >> >> >> On Mon, Aug 25, 2008 at 2:33 PM, Evan Ruff <[EMAIL PROTECTED]> wrote: >> >> >> >> > Hey Eric, >> >> >> >> > Here's the full exception log: >> >> >> >> > Uncaught exception: java.lang.ExceptionInInitializerError >> >> >> > at >> >> >> > teledini.app.client.WorkbenchEntry.onModuleLoad(WorkbenchEntry.java: >> >> >> > 70) >> >> >> > at teledini.app.client.WorkbenchEntry >> >> >> > $2.execute(WorkbenchEntry.java:63) >> >> >> > at >> >> >> > com.google.gwt.user.client.CommandExecutor.doExecuteCommands(CommandExecutor.java: >> >> >> > 311) >> >> >> > at com.google.gwt.user.client.CommandExecutor >> >> >> > $2.run(CommandExecutor.java:206) >> >> >> > at com.google.gwt.user.client.Timer.fireImpl(Timer.java:164) >> >> >> > at com.google.gwt.user.client.Timer.fireAndCatch(Timer.java:150) >> >> >> > at com.google.gwt.user.client.Timer.fire(Timer.java:142) >> >> >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> >> > at >> >> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: >> >> >> > 39) >> >> >> > at >> >> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: >> >> >> > 25) >> >> >> > at java.lang.reflect.Method.invoke(Method.java:585) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchImpl.callMethod(IDispatchImpl.java: >> >> >> > 126) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchProxy.invoke(IDispatchProxy.java: >> >> >> > 155) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchImpl.Invoke(IDispatchImpl.java: >> >> >> > 294) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchImpl.method6(IDispatchImpl.java: >> >> >> > 194) >> >> >> > at >> >> >> > org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java: >> >> >> > 117) >> >> >> > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native >> >> >> > Method) >> >> >> > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1925) >> >> >> > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java: >> >> >> > 2966) >> >> >> > at com.google.gwt.dev.GWTShell.pumpEventLoop(GWTShell.java:721) >> >> >> > at com.google.gwt.dev.GWTShell.run(GWTShell.java:594) >> >> >> > at com.google.gwt.dev.GWTShell.main(GWTShell.java:358) >> >> >> > Caused by: com.google.gwt.core.client.JavaScriptException: >> >> >> > (TypeError): Object expected number: -2146823281 description: Object >> >> >> > expected >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java: >> >> >> > 443) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java: >> >> >> > 215) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java: >> >> >> > 91) >> >> >> > at >> >> >> > com.google.gwt.maps.client.impl.__LatLngImplImpl.construct(transient >> >> >> > source for com.google.gwt.maps.client.impl.__LatLngImplImpl) >> >> >> > at com.google.gwt.maps.client.geom.LatLng.<init>(LatLng.java:65) >> >> >> > at com.google.gwt.maps.client.MapWidget.<clinit>(MapWidget.java: >> >> >> > 120) >> >> >> > at >> >> >> > teledini.app.client.WorkbenchEntry.onModuleLoad(WorkbenchEntry.java: >> >> >> > 70) >> >> >> > at teledini.app.client.WorkbenchEntry >> >> >> > $2.execute(WorkbenchEntry.java:63) >> >> >> > at >> >> >> > com.google.gwt.user.client.CommandExecutor.doExecuteCommands(CommandExecutor.java: >> >> >> > 311) >> >> >> > at com.google.gwt.user.client.CommandExecutor >> >> >> > $2.run(CommandExecutor.java:206) >> >> >> > at com.google.gwt.user.client.Timer.fireImpl(Timer.java:164) >> >> >> > at com.google.gwt.user.client.Timer.fireAndCatch(Timer.java:150) >> >> >> > at com.google.gwt.user.client.Timer.fire(Timer.java:142) >> >> >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> >> > at >> >> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: >> >> >> > 39) >> >> >> > at >> >> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: >> >> >> > 25) >> >> >> > at java.lang.reflect.Method.invoke(Method.java:585) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchImpl.callMethod(IDispatchImpl.java: >> >> >> > 126) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchProxy.invoke(IDispatchProxy.java: >> >> >> > 155) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchImpl.Invoke(IDispatchImpl.java: >> >> >> > 294) >> >> >> > at >> >> >> > com.google.gwt.dev.shell.ie.IDispatchImpl.method6(IDispatchImpl.java: >> >> >> > 194) >> >> >> > at >> >> >> > org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java: >> >> >> > 117) >> >> >> > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native >> >> >> > Method) >> >> >> > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1925) >> >> >> > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java: >> >> >> > 2966) >> >> >> > at com.google.gwt.dev.GWTShell.pumpEventLoop(GWTShell.java:721) >> >> >> > at com.google.gwt.dev.GWTShell.run(GWTShell.java:594) >> >> >> > at com.google.gwt.dev.GWTShell.main(GWTShell.java:358) >> >> >> >> > On Aug 25, 11:17 am, "Eric Ayers" <[EMAIL PROTECTED]> wrote: >> >> >> >> Hey Evan, >> >> >> >> >> This sounds kinda familiar. Can you look at the content of the >> >> >> >> exception? In hosted mode, click on the exception in the tree part >> >> >> >> of >> >> >> >> the development shell - the stack trace for the exception should >> >> >> >> display in the Status window below. If it is what I think it is - a >> >> >> >> problem in the STATUS_CODES constants, you may need to use a more >> >> >> >> recent version build from source (check it out ofSubversion) >> >> >> >> >> -Eric. >> >> >> >> >> On Mon, Aug 25, 2008 at 11:04 AM, Evan Ruff <[EMAIL PROTECTED]> >> >> >> >> wrote: >> >> >> >> >> > WHOOPS, little trigger happy. >> >> >> >> >> > The exception I get it: >> >> >> >> >> > "Uncaught Exception: java.lang.ExceptionInitilizationError" >> >> >> >> > "Caused by: >> >> ... >> >> leer más » > > > -- Eric Z. Ayers - GWT Team - Atlanta, GA USA http://code.google.com/webtoolkit/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
