The GWT 2.0.1 point release is now available for download. It contains fixes for bugs found in the 2.0.0 release.
See the GWT issue tracker for the complete list of bug fixes and enhancements in this release.
--
Miguel on behalf of the GWT Team
One question - one of the bugs listed as being fixed was 'Standard.css
missing new layout styles'.
I'm having trouble finding these new layout styles.
My expectation was that standard.css would be updated with the new
styles.
Standard.css on the 2.0.1 can be seen here:
http://code.google.com/p/google-web-toolkit/source/browse/tags/2.0.1/user/src/com/google/gwt/user/theme/standard/public/gwt/standard/standard.css
It looks identical to standard.css on 2.0.0, which can be seen here:
http://code.google.com/p/google-web-toolkit/source/browse/tags/2.0.0/user/src/com/google/gwt/user/theme/standard/public/gwt/standard/standard.css
However, standard.css on the trunk DOES seem to be updated with new
styles:
http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/theme/standard/public/gwt/standard/standard.css
Was this missed, or am i misunderstanding what this bug is referring
to?
---
Chi
On Feb 2, 7:01 pm, Miguel Méndez <mmen...@google.com> wrote:
> The GWT 2.0.1 point release is now available for download. It contains fixes
> for bugs found in the 2.0.0 release.
>
> Potentially breaking changes and fixes
>
> - Fixed a bug in how code generators collect method arguments from
> generated source, which impacted the Messages interfaces generated for
> UiBinder template files. In GWT 2.0, such argument names were incorrectly
> changed to ARGn. Most GWT applications will be unaffected, but external
> systems relying on these names may need to be updated.
> - The development mode server will, by default, only bind to localhost
> which will break cross-machine debugging. You can get the old behavior by
> specifying -bindAddress 0.0.0.0. Please see issue
> (#4322<http://code.google.com/p/google-web-toolkit/issues/detail?id=4322>)
> for more details. For webAppCreator-generated ant files, you can pass this
> with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
> - The CurrencyList/CurrencyData APIs are now public - if you were relying
> upon these classes in their non-public location, you should only need to
> update your imports.
>
> Noteworthy Fixed Issues
>
> - UiBinder Image class with resource attribute, removes styles on that
> image (#4415<http://code.google.com/p/google-web-toolkit/issues/detail?id=4415>
> )
> - Widgets lose focus if its placed on FocusPanel (Opera, Safari)
> (#1471<http://code.google.com/p/google-web-toolkit/issues/detail?id=1471>
> )
> - Standard.css missing new layout styles
> (#4429<http://code.google.com/p/google-web-toolkit/issues/detail?id=4429>
> )
> - Remove method in SplitLayoutPanel is broken
> (#4217<http://code.google.com/p/google-web-toolkit/issues/detail?id=4217>
> )
> - Splitter constructor hard codes the background color of the splitter to
> white (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
> - Image should provide method to set alternative text
> (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
> - CssResource cannot parse unescaped '-', '_' in class selectors and
> unknown at-rules
> (#3946<http://code.google.com/p/google-web-toolkit/issues/detail?id=3946>
> )
> - Focusable implementation breaks ScrollPanels in Safari
> (#1313<http://code.google.com/p/google-web-toolkit/issues/detail?id=1313>
> )
> - RequestBuilder restricted to GET and POST
> (#3388<http://code.google.com/p/google-web-toolkit/issues/detail?id=3388>
> )
> - HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with
> row and column swapped RequestBuilder restricted to GET and POST
> (#3757<http://code.google.com/p/google-web-toolkit/issues/detail?id=3757>
> )
> - MenuBar steals focus when hovered
> (#3884<http://code.google.com/p/google-web-toolkit/issues/detail?id=3884>
> )
> - TabLayoutPanel tabs don't line up properly on IE
> (#4447<http://code.google.com/p/google-web-toolkit/issues/detail?id=4447>
> )
> - webAppCreator produces ant build files which support the gwt.args
> property for passing additional flags to the gwtc and devmode rules, such as
> ant -Dgwt.args="-style PRETTY" gwtc.
>
> See the GWT issue tracker for the complete list of bug fixes and
> enhancements<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...>
On Feb 2, 9:01 pm, Miguel Méndez <mmen...@google.com> wrote:
> The GWT 2.0.1 point release is now available for download. It contains fixes
> for bugs found in the 2.0.0 release.
> ...
> - Image should provide method to set alternative text
> (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
>...
How soon do you think you can get it into the main Maven repo?
Yegor
Does the Eclipse Plugin automatically update it's SDK to 2.0.1?
Or is the update notification only related to the Plugin Version?
I dont see any updates when klicking: "Check for Updates"
in Eclipse.
Thanks,
Florian
On 3 Feb., 03:01, Miguel Méndez <mmen...@google.com> wrote:
> The GWT 2.0.1 point release is now available for download. It contains fixes
> for bugs found in the 2.0.0 release.
>
> Potentially breaking changes and fixes
>
> - Fixed a bug in how code generators collect method arguments from
> generated source, which impacted the Messages interfaces generated for
> UiBinder template files. In GWT 2.0, such argument names were incorrectly
> changed to ARGn. Most GWT applications will be unaffected, but external
> systems relying on these names may need to be updated.
> - The development mode server will, by default, only bind to localhost
> which will break cross-machine debugging. You can get the old behavior by
> specifying -bindAddress 0.0.0.0. Please see issue
> (#4322<http://code.google.com/p/google-web-toolkit/issues/detail?id=4322>)
> for more details. For webAppCreator-generated ant files, you can pass this
> with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
> - The CurrencyList/CurrencyData APIs are now public - if you were relying
> upon these classes in their non-public location, you should only need to
> update your imports.
>
> Noteworthy Fixed Issues
>
> - UiBinder Image class with resource attribute, removes styles on that
> image (#4415<http://code.google.com/p/google-web-toolkit/issues/detail?id=4415>
> )
> - Widgets lose focus if its placed on FocusPanel (Opera, Safari)
> (#1471<http://code.google.com/p/google-web-toolkit/issues/detail?id=1471>
> )
> - Standard.css missing new layout styles
> (#4429<http://code.google.com/p/google-web-toolkit/issues/detail?id=4429>
> )
> - Remove method in SplitLayoutPanel is broken
> (#4217<http://code.google.com/p/google-web-toolkit/issues/detail?id=4217>
> )
> - Splitter constructor hard codes the background color of the splitter to
> white (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
> - Image should provide method to set alternative text
> (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
> - CssResource cannot parse unescaped '-', '_' in class selectors and
> unknown at-rules
> (#3946<http://code.google.com/p/google-web-toolkit/issues/detail?id=3946>
> )
> - Focusable implementation breaks ScrollPanels in Safari
> (#1313<http://code.google.com/p/google-web-toolkit/issues/detail?id=1313>
> )
> - RequestBuilder restricted to GET and POST
> (#3388<http://code.google.com/p/google-web-toolkit/issues/detail?id=3388>
> )
> - HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with
> row and column swapped RequestBuilder restricted to GET and POST
> (#3757<http://code.google.com/p/google-web-toolkit/issues/detail?id=3757>
> )
> - MenuBar steals focus when hovered
> (#3884<http://code.google.com/p/google-web-toolkit/issues/detail?id=3884>
> )
> - TabLayoutPanel tabs don't line up properly on IE
> (#4447<http://code.google.com/p/google-web-toolkit/issues/detail?id=4447>
> )
> - webAppCreator produces ant build files which support the gwt.args
> property for passing additional flags to the gwtc and devmode rules, such as
> ant -Dgwt.args="-style PRETTY" gwtc.
>
> See the GWT issue tracker for the complete list of bug fixes and
> enhancements<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...>
> Does the Eclipse Plugin automatically update it's SDK to 2.0.1?
The SDK will be downloaded along with the plugin update, however the
plugin itself will not auto-update. You do it manually.
> Or is the update notification only related to the Plugin Version?
Yes
> I dont see any updates when klicking: "Check for Updates"
> in Eclipse.
"Check for Updates" never worked for me, but if you go to Help =>
Install New Software... and then select everything from Google's
update site it will pick up the updates.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
I uninstalled the 2.0.0 SDK plugin for Eclipse and installed the 2.0.1
version:
Google Web Toolkit SDK 2.0.1 2.0.1.v201002021445
com.google.gwt.eclipse.sdkbundle.e35.feature.2.0.1.feature.group
And now when I attempt to build my project by clicking on the little
red "GWT Compile Project" button, it fails almost immediately with
this internal error:
Compiling module com.basis.bbj.web.gwt.GWTWebClient
[ERROR] Unexpected
java.lang.NoSuchFieldError:
reportUnusedDeclaredThrownExceptionIncludeDocCommentReference
at
com.google.gwt.dev.javac.JdtCompiler.getCompilerOptions(JdtCompiler.java:
310)
at com.google.gwt.dev.javac.JdtCompiler
$CompilerImpl.<init>(JdtCompiler.java:148)
at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:
466)
at com.google.gwt.dev.javac.CompilationStateBuilder
$CompileMoreLater.compile(CompilationStateBuilder.java:142)
at
com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:
281)
at
com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:
182)
at
com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:
280)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:502)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:414)
at com.google.gwt.dev.Compiler.run(Compiler.java:201)
at com.google.gwt.dev.Compiler$1.run(Compiler.java:152)
at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:
87)
at
com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:
81)
at com.google.gwt.dev.Compiler.main(Compiler.java:159)
On Feb 3, 4:09 pm, Brett Morgan <brett.mor...@gmail.com> wrote:
> When will this update be on the Eclipse plugins site?
>
> brett
>
> 2010/2/3 Miguel Méndez <mmen...@google.com>
>
>
>
>
>
> > The GWT 2.0.1 point release is now available for download. It contains
> > fixes for bugs found in the 2.0.0 release.
>
> > Potentially breaking changes and fixes
>
> > - Fixed a bug in how code generators collect method arguments from
> > generated source, which impacted the Messages interfaces generated for
> > UiBinder template files. In GWT 2.0, such argument names were incorrectly
> > changed to ARGn. Most GWT applications will be unaffected, but external
> > systems relying on these names may need to be updated.
> > - The development mode server will, by default, only bind to localhost
> > which will break cross-machine debugging. You can get the old behavior by
> > specifying -bindAddress 0.0.0.0. Please see issue (#4322<http://code.google.com/p/google-web-toolkit/issues/detail?id=4322>)
> > for more details. For webAppCreator-generated ant files, you can pass this
> > with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
> > - The CurrencyList/CurrencyData APIs are now public - if you were
> > relying upon these classes in their non-public location, you should only
> > need to update your imports.
>
> > Noteworthy Fixed Issues
>
> > - UiBinder Image class with resource attribute, removes styles on that
> > image (#4415<http://code.google.com/p/google-web-toolkit/issues/detail?id=4415>
> > )
> > - Widgets lose focus if its placed on FocusPanel (Opera, Safari) (#1471<http://code.google.com/p/google-web-toolkit/issues/detail?id=1471>
> > )
> > - Standard.css missing new layout styles (#4429<http://code.google.com/p/google-web-toolkit/issues/detail?id=4429>
> > )
> > - Remove method in SplitLayoutPanel is broken (#4217<http://code.google.com/p/google-web-toolkit/issues/detail?id=4217>
> > )
> > - Splitter constructor hard codes the background color of the splitter
> > to white (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> > )
> > - Image should provide method to set alternative text (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> > )
> > - CssResource cannot parse unescaped '-', '_' in class selectors and
> > unknown at-rules (#3946<http://code.google.com/p/google-web-toolkit/issues/detail?id=3946>
> > )
> > - Focusable implementation breaks ScrollPanels in Safari (#1313<http://code.google.com/p/google-web-toolkit/issues/detail?id=1313>
> > )
> > - RequestBuilder restricted to GET and POST (#3388<http://code.google.com/p/google-web-toolkit/issues/detail?id=3388>
> > )
> > - HTMLTable.Cell.getElement() calls getCellFormatter().getElement()
> > with row and column swapped RequestBuilder restricted to GET and POST (
> > #3757<http://code.google.com/p/google-web-toolkit/issues/detail?id=3757>
> > )
> > - MenuBar steals focus when hovered (#3884<http://code.google.com/p/google-web-toolkit/issues/detail?id=3884>
> > )
> > - TabLayoutPanel tabs don't line up properly on IE (#4447<http://code.google.com/p/google-web-toolkit/issues/detail?id=4447>
> > )
> > - webAppCreator produces ant build files which support the gwt.args
> > property for passing additional flags to the gwtc and devmode rules, such as
> > ant -Dgwt.args="-style PRETTY" gwtc.
>
> > See the GWT issue tracker for the complete list of bug fixes and
> > enhancements<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...> in
> > this release.
>
> > --
>
> > Miguel on behalf of the GWT Team
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to google-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsubs cr...@googlegroups.com>
- The development mode server will, by default, only bind to localhost
which will break cross-machine debugging. You can get the old
behavior by
specifying -bindAddress 0.0.0.0. Please see issue
(#4322<http://code.google.com/p/google-web-toolkit/issues/detail?
id=4322>)
for more details. For webAppCreator-generated ant files, you can
pass this
with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
I just didn't understand why didn't you do the other way around:
left that untouched, and the ones having troubles with this, should
set -binAddress to 127.0.0.1
For me, that use cross-machine debugging for multi/browser tests, that
would be the preferred way.
Is there a reason for changing the default?
Regards,
Michel
On Feb 3, 3:01 am, Miguel Méndez <mmen...@google.com> wrote:
> The GWT 2.0.1 point release is now available for download. It contains fixes
> for bugs found in the 2.0.0 release.
>
> Potentially breaking changes and fixes
>
> - Fixed a bug in how code generators collect method arguments from
> generated source, which impacted the Messages interfaces generated for
> UiBinder template files. In GWT 2.0, such argument names were incorrectly
> changed to ARGn. Most GWT applications will be unaffected, but external
> systems relying on these names may need to be updated.
> - The development mode server will, by default, only bind to localhost
> which will break cross-machine debugging. You can get the old behavior by
> specifying -bindAddress 0.0.0.0. Please see issue
> (#4322<http://code.google.com/p/google-web-toolkit/issues/detail?id=4322>)
> for more details. For webAppCreator-generated ant files, you can pass this
> with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
> - The CurrencyList/CurrencyData APIs are now public - if you were relying
> upon these classes in their non-public location, you should only need to
> update your imports.
>
> Noteworthy Fixed Issues
>
> - UiBinder Image class with resource attribute, removes styles on that
> image (#4415<http://code.google.com/p/google-web-toolkit/issues/detail?id=4415>
> )
> - Widgets lose focus if its placed on FocusPanel (Opera, Safari)
> (#1471<http://code.google.com/p/google-web-toolkit/issues/detail?id=1471>
> )
> - Standard.css missing new layout styles
> (#4429<http://code.google.com/p/google-web-toolkit/issues/detail?id=4429>
> )
> - Remove method in SplitLayoutPanel is broken
> (#4217<http://code.google.com/p/google-web-toolkit/issues/detail?id=4217>
> )
> - Splitter constructor hard codes the background color of the splitter to
> white (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
> - Image should provide method to set alternative text
> (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
> )
> - CssResource cannot parse unescaped '-', '_' in class selectors and
> unknown at-rules
> (#3946<http://code.google.com/p/google-web-toolkit/issues/detail?id=3946>
> )
> - Focusable implementation breaks ScrollPanels in Safari
> (#1313<http://code.google.com/p/google-web-toolkit/issues/detail?id=1313>
> )
> - RequestBuilder restricted to GET and POST
> (#3388<http://code.google.com/p/google-web-toolkit/issues/detail?id=3388>
> )
> - HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with
> row and column swapped RequestBuilder restricted to GET and POST
> (#3757<http://code.google.com/p/google-web-toolkit/issues/detail?id=3757>
> )
> - MenuBar steals focus when hovered
> (#3884<http://code.google.com/p/google-web-toolkit/issues/detail?id=3884>
> )
> - TabLayoutPanel tabs don't line up properly on IE
> (#4447<http://code.google.com/p/google-web-toolkit/issues/detail?id=4447>
> )
> - webAppCreator produces ant build files which support the gwt.args
> property for passing additional flags to the gwtc and devmode rules, such as
> ant -Dgwt.args="-style PRETTY" gwtc.
>
> See the GWT issue tracker for the complete list of bug fixes and
> enhancements<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...>