Page History

...

With Magnolia 5.6 we have removed the old content API in some of our modules. For more details see the Removal of old Content API subpage.

...

Vaadin 8 and custom modules

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).

...

Please see also the links in the Further reading section for additional information on upgrading from Vaadin 7 to Vaadin 8.

...

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 :

...

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

...

Centralized Dependency Management for third-party modules (BOM)

In Magnolia 5.6.x you can optionally 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.

...