From f1a260b98bc837b676ef3a5b1123484ecf58e35e Mon Sep 17 00:00:00 2001 From: Henri Sara Date: Fri, 5 Aug 2016 11:20:07 +0300 Subject: Update release notes for Vaadin 8 Change-Id: I920a72c524f331b726a4beb8206fadcf3687999f --- all/src/main/templates/release-notes.html | 144 +++++++++--------------------- 1 file changed, 43 insertions(+), 101 deletions(-) (limited to 'all') diff --git a/all/src/main/templates/release-notes.html b/all/src/main/templates/release-notes.html index a6ff88e79e..76a7c47762 100644 --- a/all/src/main/templates/release-notes.html +++ b/all/src/main/templates/release-notes.html @@ -96,35 +96,24 @@ enhancements. Below is a list of the most notable changes:

- For enhancements introduced in Vaadin 7.6, see the Release - Notes for Vaadin 7.6.0. + For enhancements introduced in Vaadin 7.7, see the Release + Notes for Vaadin 7.7.0.

Incompatible or Behavior-altering Changes in @version-minor@

Known Issues and Limitations

- -

GWT Dependency Changes

- -

- The GWT dependencies for Vaadin are now provided as actual dependencies - and not bundled with Vaadin packages. This means that you can override - the GWT version in your own project if you want to. Note that the GWT Elemental - is still partially bundled with shared package to avoid having the gwt-user as a - dependency everywhere. -

- - - +

Vaadin Installation

@@ -282,40 +246,17 @@ along with the other 3rd party dependencies in the ZIP package.

-

- For pure client-side development, you only need the - vaadin-client - and - vaadin-client-compiler - JARs, which should be put to a non-deployed project library - folder, such as - lib - . You also need them if you compile the widget set for any - reason, such as using Vaadin add-ons, or create new - server-side components integrated with client-side widgets. -

- -

Migrating from Vaadin 6

+

Migrating from Vaadin 7

- All Vaadin 6 applications need some changes when migrating - to Vaadin 7. The most obvious changes are in the - application/window API and require extending either UI - or UI.LegacyApplication instead of Application. - A detailed list of migration changes are given in the Vaadin - 7 Migration Guide. + Most Vaadin 7 applications need some changes when migrating + to Vaadin 8.

-

Any custom client-side widgets need to be ported to use - the new client-server communication API, or the Vaadin 6 - compatibility API.

-

- Vaadin 6 add-ons (ones that contain widgets) do not work in - Vaadin 7 - please check the add-ons in Vaadin Directory - for Vaadin 7 support. + for Vaadin 8 support.

Vaadin @version@ Dependencies

@@ -409,8 +350,8 @@

Supported Technologies

- Vaadin 7 is compatible with Java 6 and newer. Vaadin - 7 is especially supported on the following operating + Vaadin 8 is compatible with Java 8 and newer. Vaadin + 8 is especially supported on the following operating systems:

@@ -421,34 +362,35 @@

- Vaadin 7 requires Java Servlet API 2.4 but also + Vaadin 8 requires Java Servlet API 3.0 but also supports later versions and should work with any Java application server that conforms to the standard. The following application servers are supported:

- Vaadin 7 supports the JSR-286 Portlet specification and all - portals that implement the specification should work. The - following portals are supported: + Vaadin 8 supports the JSR-286 Portlet specification and all + portals that implement the specification should work provided + they support Java 8 and Servlet 3.0. The following portals + are supported:

@@ -460,12 +402,12 @@

@@ -474,9 +416,9 @@

Vaadin SQL Container supports the following databases:

@@ -521,8 +463,8 @@ - Bug tracker
  • How - to get the source code of Vaadin
    • + href="https://vaadin.com/contribute">How to get the source + code of Vaadin -- cgit v1.2.3