Announcing GWT 1.6 Milestone 2

[Bruce Johnson]

The GWT team is happy to announce the availability of Google Web Toolkit 1.6 Milestone 2! Binary distributions are available for download directly from the GWT Google Code project.

http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=1.6+Milestone+2

If you have already tried GWT 1.6 Milestone 1, you may not notice much difference in Milestone 2. Changes have mostly been general polish and various small bug fixes. For the nitty-gritty details of the changes since the previous milestone, see the attached source control commit logs. You can also watch the GWT bug tracker for the most up-to-date list of resolved issues (http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=status:Fixed,FixedNotReleased%20milestone:1_6_RC&num=1000). As for doc, the javadoc that comes bundled with the distribution should be up-to-date, but the online Developer Guide (http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still being tweaked.

We anticipate that GWT 1.6 M2 will be the last milestone build for this version. After a few more bugs fixes and a bit more doc, we expect it to be followed soon by a release candidate build. In the meanwhile, please report bugs to the GWT issue tracker (http://code.google.com/p/google-web-toolkit/issues/list) after doing a quick search to see if your issue has already been reported. If you encounter a bug in 1.6 M2 that you think qualifies as a showstopper, we would greatly appreciate it if you'd also reply on this thread to alert the engineering team.

As always, remember that GWT milestone builds like this are use-at-your-own-risk. Don't be surprised if it takes a bit of trial and error to get everything to work, and we don't recommend it for production use quite yet. 

-- Bruce, on behalf of the GWT team

[Robert Cooper]

I'm getting a segfault (Leopard, java 1.5 (-d32)) trying to run the
HostedMode class. Any hints?

On Feb 24, 5:32 pm, Bruce Johnson <br...@google.com> wrote:
> The GWT team is happy to announce the availability of Google Web Toolkit
> 1.6 Milestone 2! Binary distributions are available for download directly
> from the GWT Google Code project.
>

> http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=1....

>
> If you have already tried GWT 1.6 Milestone 1, you may not notice much
> difference in Milestone 2. Changes have mostly been general polish and
> various small bug fixes. For the nitty-gritty details of the changes since
> the previous milestone, see the attached source control commit logs. You can
> also watch the GWT bug tracker for the most up-to-date list of resolved

> issues (http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...).

> As for doc, the javadoc that comes bundled with the distribution should be
> up-to-date, but the online Developer Guide (http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still
> being tweaked.
>
> We anticipate that GWT 1.6 M2 will be the last milestone build for this
> version. After a few more bugs fixes and a bit more doc, we expect it to be
> followed soon by a release candidate build. In the meanwhile, please report
> bugs to the GWT issue tracker (http://code.google.com/p/google-web-toolkit/issues/list) after doing a quick
> search to see if your issue has already been reported. If you encounter a
> bug in 1.6 M2 that you think qualifies as a showstopper, we would greatly
> appreciate it if you'd also reply on this thread to alert the engineering
> team.
>
> As always, remember that GWT milestone builds like this are
> use-at-your-own-risk. Don't be surprised if it takes a bit of trial and
> error to get everything to work, and we don't recommend it for production
> use quite yet.
>
> -- Bruce, on behalf of the GWT team
>

>  svn-log-since-r4621.zip
> 6KViewDownload

[Scott Blum]

Robert, did you get this crash with Milestone 1?  If you didn't run Milestone 1, would you mind trying it out?

[Robert Cooper]

I ran M1 and didn't get it, but at the time, I was still running
GWTShell and dealing with the deprecated warning.

Below is my launch script (if someone sees something glaringly wrong I
have missed)

export CLASSPATH="/Users/kebernet/Applications/gwt-mac-1.6.1/gwt-
user.jar":"/Users/kebernet/Applications/gwt-mac-1.6.1/gwt-dev-
mac.jar":"/Users/kebernet/Documents/code/gwittir/gwittir/gwittir-core/
src/main/java":"/Users/kebernet/Documents/code/gwittir/gwittir/gwittir-
core/src/main/resources":"/Users/kebernet/Documents/code/gwittir/
gwittir/gwittir-core/classes":"/Users/kebernet/Documents/code/gwittir/
gwittir/gwittir-core/target/classes"

/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/
java" -XstartOnFirstThread -Xmx512m -cp $CLASSPATH -Dcatalina.base="/
Users/kebernet/Documents/code/gwittir/gwittir/gwittir-core/target/
tomcat" com.google.gwt.dev.HostedMode -gen /Users/kebernet/Documents/
code/gwittir/gwittir/gwittir-core/target/gwtgen -logLevel INFO -style
OBF -workDir /Users/kebernet/Documents/code/gwittir/gwittir/gwittir-
core/target/gwtWork -extra /Users/kebernet/Documents/code/gwittir/
gwittir/gwittir-core/target/gwtExtra -war "/Users/kebernet/Documents/
code/gwittir/gwittir/gwittir-core/target/gwittir-core-0.4.2" -
localWorkers 2 -port 8088 -startupUrl /strict.html?log.level=spam
com.totsp.gwittir.example.Example

On Feb 24, 10:31 pm, Scott Blum <sco...@google.com> wrote:
> Robert, did you get this crash with Milestone 1?  If you didn't run
> Milestone 1, would you mind trying it out?
>

[Robert Cooper]

And I have tried it with both -d32 and -d64 on Leopard.

[nicolas de loof]

I notice running the Hosted mode server with wrong parameters output a help message with :

-server        Prevents the embedded Tomcat server from running, even if a port is specified

But Tomcat is supposed to have been replaced by Jetty, isn't it :D

[Scott Blum]

That looks fine to me, although that -Dcatalina.base shouldn't matter anymore.  Can you send me a VM crash log?

[Scott Blum]

Huh, that should have been fixed in M2.  It should now say "Specify the TCP port for the embedded web server (defaults to 8888)".  Are you sure that's still an issue in M2?

[nicolas de loof]

I'm using M2 !

Unknown argument: -foo

Google Web Toolkit 1.6.1

HostedMode [-noserver] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logLevel level] [-gen dir] [-style style] [-ea] [-server servletContainerLauncher] [-startupUrl url] [-war dir] [-extra dir] [-workDir dir] [-localWorkers count] module[s] 

where 

  -noserver      Prevents the embedded web server from running

  -port          Specify the TCP port for the embedded web server (defaults to 8888)

  -whitelist     Allows the user to browse URLs that match the specified regexes (comma or space separated)

  -blacklist     Prevents the user browsing URLs that match the specified regexes (comma or space separated)

  -logLevel      The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL

  -gen           The directory into which generated files will be written for review

  -style         Script output style: OBF[USCATED], PRETTY, or DETAILED (defaults to OBF)

  -ea            Debugging: causes the compiled output to check assert statements.

  -server        Prevents the embedded Tomcat server from running, even if a port is specified

  -startupUrl    Automatically launches the specified URL

  -war           The war directory to write output files into (defaults to war)

  -extra         The directory into which extra, non-deployed files will be written

  -workDir       The compiler work directory (must be writeable; defaults to a system temp dir)

  -localWorkers  Specifies the number of local workers to use whe compiling permutations

and 

  module[s]      Specifies the name(s) of the module(s) to host

[Scott Blum]

On Wed, Feb 25, 2009 at 11:41 AM, nicolas de loof <nicolas...@gmail.com> wrote:

I'm using M2 !

where 

  -noserver      Prevents the embedded web server from running

  -port          Specify the TCP port for the embedded web server (defaults to 8888)

  -server        Prevents the embedded Tomcat server from running, even if a port is specified

Ooooh, okay.  I was looking in the wrong place.  It looks like it's the help text for -server that's actually wrong.  Will fix, thanks.