Release Notes / Version 13.2512.0
Table Of Contents
A banDuplicateClasses rule has been added to the
maven-enforcer-plugin configuration to avoid
multiple classes with the same Fully Qualified Class
Name to be on the classpaths of the CoreMedia applications.
The Extra Enforcer Rules: Ban Duplicate Classes rule has been added to the Maven Enforcer plugin’s configurations in the CoreMedia CMS workspaces to ensure that multiple dependencies with the same classes cannot be added to production classpaths of the Maven modules. Test classpaths are ignored from this check.
To satisfy this check, some project dependencies had to be cleaned up. Notable duplicates:
org.apache.tomcat.embed:tomcat-embed-coreshades thejakarta.servlet:jakarta.servlet-api: The Embedded Core Tomcat implementation must be added to the Spring Boot JARs of the CoreMedia CMS applications and thus the Jakarta Servlet API dependency cannot be added there. In the project’s (non-app) Maven modules, the Jakarta Servlet API is added with provided scope except where the embedded Core Tomcat implementation is also needed. This was already the case in almost all modules in the blueprint workspace, only a few minor adjustments had to be made.org.apache.tomcat:tomcat-annotations-apivs.jakarta.annotation:jakarta.annotation-api: The Jakarta Annotation API is preferred over the Tomcat Annotations API, transitive dependencies of latter have been removed.
(CMS-28147)
