Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
...
TextField
).Change the vaadin-server
dependency from
Code Block | ||
---|---|---|
| ||
<dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-server</artifactId> <version>7.7.6</version> </dependency> |
to
Code Block | ||
---|---|---|
| ||
<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:
Code Block | ||
---|---|---|
| ||
<dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-server</artifactId> <version>8.1.5</version> </dependency> |
...
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.
...
The 5.6 branch brings the Publishing module pack (see publishing
on Git) , which is intended to replace replaces the Activation module ( /modules/activation
) and the Transactional Activation module ( /modules/exchange-transactional
). Besides giving a more logical ordering to the publishing functions in Magnolia, the new module pack also sets all workspaces as publishable by default. For an overview and comparison please see Publishing and activation.
...