Page History

...

1. 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
   Style boxed
   <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-server</artifactId> <version>7.7.6</version> </dependency>

   to 

   Mgnl mini code snippet
   Style boxed
   <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

   To be able to use the new Vaadin 8 features, add also the following dependency:

   Mgnl mini code snippet
   Style boxed
   <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-server</artifactId> <version>8.0.0</version> </dependency>

   
   

Vaadin widget sets

Vaadin7WidgetSet

Normally, you won't need to do this 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" /> .

MagnoliaProWidgetSet vs MagnoliaWidgetSet

...

magnolia.ui.vaadin.widgetset=info.magnolia.widgetset.MagnoliaWidgetSet

Vaadin7WidgetSet

Normally, you won't need to do this 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 :

...

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

...

Centralized Dependency Management for third-party modules (BOM)

Following the release of Magnolia 5.5.7, Magnolia 5.6.x allows you optionally to define third-party dependencies in a different way. Previously, dependency management information about third-party modules was defined in the parent poms of magnolia.main and magnolia.ui . You may now use a software BOM (Bill of materials) project instead. The project can then be imported in all modules. This ensures that the versions of the third-party modules are the same.

...