[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-17 Thread Scott Blum
Jeff: previously everything we shipped in gwt-dev-*.jar was accessible to server code. With the new entry point, we isolate the web application so that you'll be explicit about your dependencies.. this make it much more likely that when you deploy your GWT app to a real server, things just work

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-15 Thread Jeff J.
Scott, Your mentioned solution of copying gwt-servlet.jar into WEB-INF/lib did work for the webAppCreator project, however my existing large project still has the ClassNotFoundException for org.apache.xerces.jaxp.SAXParserFactoryImpl. I am still at a loss of ideas, as gwt-user.jar,

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-15 Thread Jeff J.
Update: I've fixed the issue by simply including xercesImpl.jar from GWT Tools in WEB-INF/lib. Still not exactly sure why it is needed now and not previously, but it is working right now in hosted mode so all is good. Thanks, Jeff On Feb 15, 11:13 pm, Jeff J. jsjenkins...@gmail.com wrote:

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-13 Thread Jeff J.
I'm getting class not found exceptions when trying to launch my project in hosted mode using this build, saying Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found. I tried to create a fresh new project using webAppCreator and I get NoClassDefFoundError looking for

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-13 Thread Scott Blum
Not sure what might be causing the SAX problem. Can you file an issue with more detailed information? The NoClassDefFound is caused by not copying gwt-servlet.jar into WEB-INF/lib. If you run the ant build file, it will do this automatically, but we have a fix in place for the next milestone

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-06 Thread nicolas de loof
Your example works, The issue is that I don't load the class from a classloader, I'm using BCEL to read the .class and access the GWT_VERSION_NUM field, so static initializer is not executed. I now fallback to reading the About.properties if present, this fix my version-detection issue Cheers,

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-06 Thread Scott Blum
LOL, well that would explain it. :) To be fair, in previous versions this would have worked since those fields were (I think wrongly) compile-time-constants. On Fri, Feb 6, 2009 at 3:10 AM, nicolas de loof nicolas.del...@gmail.comwrote: Your example works, The issue is that I don't load the

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-06 Thread Matthew Mastracci
Scott et. al, Great release! I spent a few hours migrating our codebase and build process without much trouble. 1. The new expanded WAR format makes life a lot easier for us to run with -noserver. With 1.5, we had to regenerate the hosted.html and nocache.js files every time something

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-06 Thread Scott Blum
On Fri, Feb 6, 2009 at 12:30 PM, Matthew Mastracci matt...@mastracci.comwrote: 2. The compiler task crashes Java 1.6 on Mac now. The previous versions would run fine with the 64-bit JVM (even though SWT isn't compatible). Would it be possible to lazy load SWT so that we can take advantage

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-05 Thread nicolas de loof
I just notice the About class has not the GWT_VERIOSN_NUMBER set. Seems the code expects some String replacement for @gwt_vers...@. I'm using About.GWT_VERSION_NUM constant in gwt-maven-plugin to detect the GWT version used when user provides it's own implementation. Cheers, Nicolas On Thu, Feb

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-05 Thread stuckagain
Hi, As a confidence test I tried to compile our projects with the new release and failed miserably. Is it expected that the GWT JavaScript compiler now seems to use native code ? Is this to support compiling in multiple processes ? Or is it a sideeffect of some other changes ? I normally build

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-05 Thread Arthur Kalmenson
Congratulations! I'll try to give this a swing this week or next week, I hope it doesn't break the gwt-maven plugin too badly. Does anyone know when this milestone will hit the central Maven repo? -- Arthur Kalmenson On Wed, Feb 4, 2009 at 7:34 PM, Scott Blum sco...@google.com wrote:

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-05 Thread Emily Crutcher
Only the current gwt-incubator trunk is validated to work against the release jar. We'll be releasing a new gwt-incubator jar soon, but I'm still working on getting all the demos to build and display correctly. On Thu, Feb 5, 2009 at 12:24 PM, Scott Blum sco...@google.com wrote: Hi stuckagain,

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-05 Thread Scott Blum
By the way, I should point out that Maven integration might be easier in the future. http://code.google.com/p/google-web-toolkit/issues/detail?id=1032 On Thu, Feb 5, 2009 at 9:35 AM, Arthur Kalmenson arthur.k...@gmail.comwrote: Congratulations! I'll try to give this a swing this week or next

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-05 Thread Scott Blum
Nicolas, I can't reproduce the issue you're seeing. Do you have a weird classloader setup? Or is it possible the code you have that references About needs to be recompiled? Try the following test.. create a Main.java in your GWT install directory and run the following commands. Main.java:

[gwt-contrib] Re: Announcing GWT 1.6 Milestone 1

2009-02-04 Thread Ray Cromwell
Congratulations on the milestone release! I think some beers are in order. :) -Ray On Wed, Feb 4, 2009 at 4:34 PM, Scott Blum sco...@google.com wrote: Greetings GWT developers, The GWT team is happy to announce the availability of 1.6 Milestone 1! Binary distributions are available for