Revision: 6989
Author: [email protected]
Date: Wed Nov 18 09:08:21 2009
Log: Separated HtmlUnit layout issue from GPE issue.
http://code.google.com/p/google-web-toolkit/source/detail?r=6989
Modified:
/wiki/GWT_2_0_RC.wiki
=======================================
--- /wiki/GWT_2_0_RC.wiki Tue Nov 17 11:34:47 2009
+++ /wiki/GWT_2_0_RC.wiki Wed Nov 18 09:08:21 2009
@@ -148,7 +148,8 @@
* Prior to 2.0, GWT tools such as the compiler were provide in a
platform-specific jar (that is, with names like `gwt-dev-windows.jar`). As
of 2.0, GWT tools are no longer platform specific and they reside in
generically-named `gwt-dev.jar`. You are quite likely to have to update
build scripts to remove the platform-specific suffix, but that's the extent
of it.
* The development mode entry point has changed a few times since GWT
1.0. It was originally called `GWTShell`, and in GWT 1.6 a replacement
entry point called `HostedMode` was introduced. As of GWT 2.0, to reflect
the new "development mode" terminology, the new entry point for development
mode is `com.google.gwt.dev.DevMode`. Sorry to keep changing that on ya,
but the good news is that the prior entry point still works. But, to really
stay current, we recommend you switch to the new `DevMode` entry point.
* Also due to the "development mode" terminology change, the name of the
ant build target produced by `webAppCreator` has changed from `hosted` to
`devmode`. In other words, to start development mode from the command-line,
type `ant devmode`.
- * !HtmlUnit does not attempt to emulate authentic browser layout.
Consequently, tests that are sensitive to browser layout are very likely to
fail. However, since GWTTestCase supports other methods of running tests,
such as Selenium, that do support accurate layout testing, it can still
make sense to keep layout-sensitive tests in the same test case as
non-layout-sensitive tests. If you want such tests to be ignored
by !HtmlUnit, simply annotate the test methods with
@!DoNotRunWith({Platform.!HtmlUnit}). Versions of Google Plugin for Eclipse
prior to 1.2 will only allow you to add GWT release directories that
include a file with a name like `gwt-dev-windows.jar`. You can fool it by
sym linking or copying gwt-dev.jar to the appropriate name.
+ * !HtmlUnit does not attempt to emulate authentic browser layout.
Consequently, tests that are sensitive to browser layout are very likely to
fail. However, since GWTTestCase supports other methods of running tests,
such as Selenium, that do support accurate layout testing, it can still
make sense to keep layout-sensitive tests in the same test case as
non-layout-sensitive tests. If you want such tests to be ignored
by !HtmlUnit, simply annotate the test methods with
@!DoNotRunWith({Platform.!HtmlUnit}).
+ * Versions of Google Plugin for Eclipse prior to 1.2 will only allow you
to add GWT release directories that include a file with a name like
`gwt-dev-windows.jar`. You can fool it by sym linking or copying
gwt-dev.jar to the appropriate name.
* The way arguments are passed to the GWT testing infrastructure has
been revamped. There is now a consistent syntax to support arbitrary "run
styles", including user-written, with no changes to GWT itself. For
example, `-selenium FF3` has become `-runStyle selenium:FF3`. This change
likely does not affect typical test invocation scripts, but if you do use
`-Dgwt.args` to pass arguments to GWTTestCase, be aware that you may need
to make some changes.
* When using !ClientBundle, be aware that images using alpha
transparency do not appear transparent in IE6. The Mail sample application
included in the GWT distribution currently suffers from this limitation
(that is, the images have opaque backgrounds when viewed on IE6).
* Users of the Google Plugin for Eclipse that are running Google App
Engine projects in development mode may see errors like "Unable to
find 'myapp.gwt.xml' on your classpath; could be a typo, or maybe you
forgot to include a classpath entry for source?". (Note that the app name
has been cast to lowercase, that's a symptom.) This is due to an
unfortunate interaction between weak references to module definitions and
garbage collection kicked off by the App Engine.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
