From fb63a60cc40133a0062dd77b9694d80b1b39155c Mon Sep 17 00:00:00 2001 From: Teemu Suo-Anttila Date: Mon, 2 May 2016 14:30:42 +0300 Subject: Use gwt-user and gwt-dev dependencies in client and compiler This removes GWT dependency from the server and shared parts of the framework Change-Id: Iafbb752c0184611a18d4a9d61c9e03229d42836e --- all/src/main/templates/release-notes.html | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) (limited to 'all/src') diff --git a/all/src/main/templates/release-notes.html b/all/src/main/templates/release-notes.html index 8c2a7d653e..9d942d3134 100644 --- a/all/src/main/templates/release-notes.html +++ b/all/src/main/templates/release-notes.html @@ -48,6 +48,7 @@
  • Incompatible or Behavior-altering Changes in @version-minor@
  • Known Issues and Limitations
  • +
  • GWT Dependency Changes
  • Vaadin Installation
  • Package Contents
  • Migrating from Vaadin 6
  • @@ -115,6 +116,7 @@
  • The return type of BootstrapHandler.getWidgetsetForUI() has changed.
  • Vaadin shared no longer depends on a custom build of Guava. Any project that depends on Guava as a transitive dependency should use standard Guava.
  • Valo theme field error styles now apply to NativeSelect, ListSelect and TwinColSelect as well.
  • +
  • The way we handle GWT dependencies has been completely changed. See this section for more details
  • 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

    -- cgit v1.2.3