Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
14.6.0
-
None
-
None
-
Pulsar
-
Pulsar 266 - ContentType API 3
Description
A 14.6.0 archetype project has two jars by the same name, but different version in the WEB-INF/lib:
spring-boot-14.6.0.jar spring-boot-2.4.4.jar
This can be confusing and is potentially problematic.
The former one is from artifact org.onehippo.cms7:spring-boot in the community/cms/spring-boot module.
Let's be consistent and prefix the artifact with hippo-cms-.
Second, we have some Tomcat-specific jars now:
spring-boot-starter-tomcat-2.4.4.jar tomcat-embed-core-9.0.44.jar tomcat-embed-websocket-9.0.44.jar
I'm not saying that these must not be there, but are these necessary?
Attachments
Issue Links
- relates to
-
CMS-14724 14.6 Spring Boot doesn't work with existing Spring contexts, breaks minor upgrade
-
- Closed
-