Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Update to your latest minor release version first before upgrade to recent major release. For example as of May 2017, a customer would like to upgrade from 5.4.1 to 5.5.4 (latest release at that time), then the correct sequence would be 5.4.8 → 5.4.12 → 5.5.4 instead of  5.4.8 → 5.5 → 5.5.3.
  2. Carefully look for "change" or "changes for ..." sections in the Release notes since that changes is necessary in this specific case when you are updating from 5.4.1 solely.
  3. Because upgrading process takes time and vulnerable to incidents, please minimize the risk by clean up your system, remove unused data, reindex everything and do a full backup first.

Specific points

Vaadin

Ugrading from Vaadin 7 to Vaadin 8

...

If upgrading from a pre-5.6

...

verison to Magnolia 5.6

...

+, you will have to  begins with Vaadin 8.1.5

...

 (see Vaadin

...

8.1.5

...

release

...

notes

...

Vaadin 8.1.5 DOCS: https://vaadin.com/download/release/8.1/8.1.5/docs/api/

...

titleMain 8.1 (8.0.0) enhancements (features)

...

and

...

API docs), you ...


  1. You should check whether and which of your modules contain Vaadin implementations.
  2. If they do, get the https://github.com/vaadin/framework8-migration-tool .
    1. Install it locally and run like a Java jar afterwards.
    2. The script automatically changes the imports of the affected classes and thus – in the majority of cases – will make your module(s) compatible with Vaadin 8.
  3. As stated on https://vaadin.com/docs/framework/migration/migrating-to-vaadin8.html, some dependencies have to be added in order to use compatible classes from Vaadin 7 (such as TextField .)

    Change the vaadin-server dependency from 

    Mgnl mini code snippet
    Styleboxed

    <dependency>
    <groupId>com.vaadin</groupId>
    <artifactId>vaadin-server</artifactId>
    <version>7.7.6</version>
    </dependency>

    to 

    Mgnl mini code snippet
    Styleboxed

    <dependency>
    <groupId>com.vaadin</groupId>
    <artifactId>vaadin-compatibility-server</artifactId>
    <version>8.0.0</version>
    </dependency>

    The full list of compatibility packages available for Framework 8:

    • vaadin-compatibility-server
    • vaadin-compatibility-client
    • vaadin-compatibility-client-compiled
    • vaadin-compatibility-shared
    • vaadin-compatibility-themes

    (lightbulb) To be able to use the good new Vaadin 8 features, add also:

    Mgnl mini code snippet
    Styleboxed

    <dependency>
    <groupId>com.vaadin</groupId>
    <artifactId>vaadin-server</artifactId>
    <version>8.0.0</version>
    </dependency>


  4. (warning) Normally, you won't need this step since you have a Magnolia running for you. However, in case you are demoing your module as a custom Vaadin application, then you have to include Vaadin7WidgetSet :

    1. Either annotate the UI class as such with @Widgetset("com.vaadin.v7.Vaadin7WidgetSet"),

    2. or do it in your GW[i]T configuration file by adding <inherits name="com.vaadin.v7.Vaadin7WidgetSet" /> .

...