Relevant Changes in Bloomreach Content 17

This page outlines the key changes introduced in Bloomreach Content 17 compared to version 16.

Major Changes

Java 21 Requirement

Bloomreach Content 17 requires Java 21. If you deploy your project on the Bloomreach Cloud hosting platform, the platform automatically detects and uses the correct Java version for your uploaded distribution.

Spring Boot 4 Upgrade

Version 17 uses Spring Boot 4, Spring Framework 7, and Spring Security 7. If your project includes custom Spring configuration, custom Spring beans, or Spring Security customizations, review the Spring Boot 4 and Spring Security 7 migration guides to identify and implement required changes.

Spring AI is now at version 2.0. If your project uses the AI Content Assistant with custom AI extensions (such as custom AIModelFactory, VectorStoreFactory, or ClientToolPackage implementations), review the Spring AI 2.0 release notes for API changes.

Jackrabbit RMI Support Removed

Bloomreach Content 17 uses Jackrabbit 2.22.2, which no longer supports RMI. For details, see JCR-4972.

If your project connects to the repository using RMI, switch to an alternative connection method before upgrading.

Migration to JUnit Jupiter 6

JUnit 4 has been replaced with JUnit Jupiter 6.0.3. The parent POM (hippo-cms7-project) no longer manages junit:junit in <dependencyManagement>. JUnit Jupiter libraries (junit-jupiter-api, junit-jupiter-engine, junit-jupiter-params) are now managed at version 6.0.3.

If your test code uses JUnit 4 annotations (such as @RunWith or org.junit.Test), migrate your tests to JUnit Jupiter before upgrading.

OpenTelemetry Integration

Version 17 adds native OpenTelemetry support. Distributed traces are collected automatically using the standard Java auto-instrumentation agent and can be sent to any OTLP-compatible backend. This feature is opt-in and does not require code changes. For configuration instructions, see the OpenTelemetry setup documentation.

Content REST API Workflow Fields Removed

The following internal workflow fields are no longer included in Content REST API responses as of version 17.0:

hippostdpubwf:publishedBy
hippostdpubwf:depublishedBy
hippostdpubwf:publicationReason
hippostdpubwf:depublicationReason

These fields were not part of the documented public API contract but were previously visible in responses. Their removal prevents user identity information from being exposed in delivery applications.

Impact: If your delivery application reads any of these fields from the Content REST API, those fields will return no value after upgrading. No error or warning is generated. Review and update your delivery-layer code to remove any references to these fields before upgrading.

Essentials Setup Wizard Migration to Angular 21

The Essentials setup wizard has been rebuilt from AngularJS to Angular 21. Most projects do not require changes. However, if your project includes custom Essentials plugins with a frontend component—specifically, an AngularJS controller registered to the hippo.essentials module and an HTML fragment packaged as a web fragment under META-INF/resources—these frontend components will no longer function and must be rewritten for Angular 21 before upgrading.

Removed Modules

The following modules have been removed from the repository:

Targeting Demo Support (com.onehippo.cms7:hippo-addon-targeting-demo-support):
The data-loader and data-generator demo submodules have been removed. Remove any references to these artifacts from your project before upgrading:

com.onehippo.cms7:hippo-addon-targeting-demo-support-data-loader
com.onehippo.cms7:hippo-addon-targeting-demo-support-data-generator

Frontend Theme:
The frontend-theme module has been removed. If your project references files from this module, update your project to remove those dependencies.

Minor Changes

Chinese (Simplified) UI translation files (_zh variants) have been removed. The CMS UI will default to English for any labels that previously had a Chinese translation. Custom project translations are not affected.
HikariCP has been upgraded to version 7.0.0 or later. No action is required; this resolves reliability issues present in earlier versions.
APIs previously marked as deprecated and scheduled for removal have been removed in this release. Review your project for usage of deprecated APIs and update as needed before upgrading.
Third-party libraries have been updated.

For a complete list of changes, see the detailed release notes.