Details
-
Bug
-
Resolution: Not an issue
-
Major
-
None
-
None
-
None
-
None
Description
When using magnolia-bundled-webapp 5.3.2 as a POM type dependency, it brings in wrong dependency versions for:
- magnolia-ui-framework version
- magnolia-ui-contentapp
- magnolia-rendering
That's hard to find out for newbies, and cumbersome to add the exclusions and then having to add explicit dependencies on the 5.3.2 versions manually. The workaround is the following:
<dependency> <groupId>info.magnolia.eebundle</groupId> <artifactId>magnolia-enterprise-webapp</artifactId> <type>pom</type> <exclusions> <!-- see comment in next dependency --> <exclusion> <artifactId>magnolia-ui-framework</artifactId> <groupId>info.magnolia.ui</groupId> </exclusion> <exclusion> <artifactId>magnolia-ui-contentapp</artifactId> <groupId>info.magnolia.ui</groupId> </exclusion> <exclusion> <artifactId>magnolia-rendering</artifactId> <groupId>info.magnolia</groupId> </exclusion> </exclusions> </dependency> <!-- must exclude wrong magnolia dependencies versions brought in by magnolia-enterprise-webapp above and explicitly depend on 5.3.2 versions of those dependencies until http://jira.magnolia-cms.com/browse/MAGNOLIA-5902 is fixed --> <dependency> <artifactId>magnolia-ui-framework</artifactId> <groupId>info.magnolia.ui</groupId> <version>${magnolia.version}</version> </dependency> <dependency> <artifactId>magnolia-ui-contentapp</artifactId> <groupId>info.magnolia.ui</groupId> <version>${magnolia.version}</version> </dependency> <dependency> <artifactId>magnolia-rendering</artifactId> <groupId>info.magnolia</groupId> <version>${magnolia.version}</version> </dependency>
Without this workaround Magnolia will complain about incompatible module versions during startup.
Checklists
Acceptance criteria