From 648cc89d907d9e493df2292fa8fa0a5f12b3f255 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Marko=20Gr=C3=B6nroos?= Vaadin @version@ is the first update release for Vaadin 6. In addition to many bug
+ Vaadin @version@ is the first feature update release for Vaadin 6. In addition to many bug
fixes, the most significant additions are:
See the Change Log below for a more detailed list of closed issues in this release.
-Vaadin @version@ uses Google Web Toolkit 1.7.0, which is included in the gwt folder of the installation package.
+Vaadin @version@ uses Google Web Toolkit 1.7.0, which is included in the gwt folder of the installation package. The plugin downloads the new version automatically (you may need to update your widget set compilation scripts and launch configurations).
The previous version of the VButton widget (i.e. GWT counterpart for the Button component) was built using the native BUTTON element in the browser. Because of multiple theming issues that resulted from that (final nail in the coffin, #3079), the implementation was changed to a DIV based one.
@@ -138,7 +141,13 @@ fixes, the most significant additions are:The compilation of OOPHM widget sets uses a large amount of stack memory, so if the -JVM default is too small, you should set it explicitly in compile-widgetset.xml -with the following parameter for the Java process (currently included in the example build -script): <jvmarg value="-Xss1024k"/>.
+The GWT 1.7.0 version included in the OOPHM package is a custom +build from GWT trunk and is not 100% compatible with the official GWT +1.7.0 release (#3270).
As the OOPHM package is experimental, you should use it only for debugging purposes during development. For production use, you should @@ -263,33 +270,6 @@ for your platform.
GWT code. You need to install the experimental OOPHM package instead (see above) for development. For production, you should use the regular package for Linux.#2523: GWT Compiler 1.7 uses more - stack space than 1.5 and can result in stack overflow errors. You can prevent the - problem by giving the Java process more stack space with the -Xss - parameter, such as: -Xss1024k. You can give the parameter in your widgetset - build script with a <jvmarg value="-Xss1024k"/> parameter for the - <java> task.
#2891: As there is a bug in - J2SE 5.0 that prevents setting the stack size for the main thread, widgetsets - cannot be compiled using the standard GWT compiler of GWT 1.7 and JDK 1.5.0 (see - #2656 for more details on the JDK - bug). This bug primarily affects Windows users as other operating systems have a - larger default stack size.
- -Before that fix is available in a published GWT version, we provide a wrapper - for the GWT compiler that runs the compiler in a separate thread, thus using the - user-specified stack size settings also on JDK 1.5.0. Use - com.itmill.toolkit.launcher.WidgetsetCompiler instead of - com.google.gwt.dev.Compiler. You need the wrapper if you use a build - script to compile custom widget sets; the Eclipse plugin uses the wrapper - automatically. You can also avoid the problem by using JDK 1.7.
-For other known problems, see open tickets at developer site