Page History

...

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

1. Check whether and which of if your modules contain Vaadin implementations.
2. If they do:
   1. Obtain the https://github.com/vaadin/framework8-migration-tool .
   2. Install it locally and run like a Java jar.
   3. 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.htmlin Migrating to Vaadin 8, some dependencies need to be added in order to use the 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.1.5</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.1.5</version> </dependency>

   
   

...