Page History

...

If upgrading from a pre-5.6 verison Magnolia version to Magnolia the 5.6 +, you will have to  begins with branch, please follow the steps below to make use that your custom modules are compatible with the UI in this branch. The first Magnolia release in this branch uses Vaadin 8.1.5 (see Vaadin 8.1.5 release notes and API docs), you ...

1. You should check 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 good new Vaadin 8 features, add also:

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

   
   

4. 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" /> .

The

...

Vaadin widgetset

In the Enterprise Edition Pro

If you had EE Pro 5.4.x or previous and are installing EE Pro 5.6: Due to component personalization bringing in new features to the page editor.x, you must replace the widgetset in the magnolia.properties file . Either due to component personalization bringing in new features to the page editor. Either replace or add (depending on the update path):

magnolia.ui.vaadin.widgetset=info.magnolia.widgetset.MagnoliaProWidgetSet

In the Community Edition

The Community Edition uses the MagnoliaWidgetSet :

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

Centralized Dependency Management for third-party modules (BOM)

...