Red Hat Training

A Red Hat training course is available for Red Hat OpenShift Application Runtimes

RHOAR Spring Boot 1.5.x Release Notes

Red Hat OpenShift Application Runtimes 1

For use with Red Hat OpenShift Application Runtimes Spring Boot 1.5.x

Red Hat Customer Content Services


This Release Note contains important information related to Red Hat OpenShift Application Runtimes Spring Boot 1.5.x


Date of release: 2018-12-06

Chapter 1. Required Infrastructure Component Versions

The following versions of infrastructure components are required for all runtimes distributed as part of a RHOAR release. Red Hat does not provide support for components listed below, with the exception of components explicitly designated as supported.

Component nameVersion



Fabric8 Maven Plugin



OpenJDK 8[c]

OpenShift Container Platform (OCP)[d]

3.11 or later


1.34.0 or later




2.0 or later

oc command line tool

3.11 or later[f]

[a] A full JDK installation is required, as JRE does not provide tools for compiling Java applications from source.
[b] Red Hat OpenJDK is supported by Red Hat
[c] OpenJDK 9 is not supported by Red Hat.
[d] OCP is supported by Red Hat
[e] CDK is supported by Red Hat
[f] The version of the oc CLI tool should correspond to the version of OCP that you are using.

Chapter 2. Supported Spring Boot Runtime Component Configurations and Integrations

The following resource defines the supported configurations and integrations of Red Hat products with RHOAR Spring Boot:

Chapter 3. Features

3.1. New and Changed features

No new notable features are introduced in this release.

3.2. Deprecated features

No features or functionalities are marked as deprecated in this release.

3.3. Technology preview

Deploying Spring Boot applications on Red Hat JBoss Fuse
As a Technology Preview feature, RHOAR allows you to build and deploy Spring Boot applications packaged as JAR files on Red Hat JBoss Fuse, both in stand-alone mode and on OpenShift. For additional information, see Red Hat JBoss Fuse documentation.
Building and Deploying Spring Boot Application WAR Files
The Spring Boot plugin allows you to deploy your Spring Boot Applications as WAR files. This feature is not supported for use in production environments.

Chapter 4. Release components

4.1. Supported Artifacts introduced in this release

No new supported artifacts are introduced in this release.

4.2. Technology Preview artifacts introduced in this release

No Technology Preview artifacts are introduced in this release.

4.3. Artifacts removed in this release

No supported artifacts are removed in this release.

4.4. Artifacts deprecated in this release

No artifacts are marked as deprecated in this release.

Chapter 5. Fixed issues

This RHOAR Spring Boot release incorporates all bugfixes from the upstream release. Issues resolved in the community release are listed in the Spring Boot 1.5 Release Notes.

The following issue has been resolved as part of the RHOAR Spring Boot 1.5.19 product release:

  • SB-1390: Artifact org.infinispan:infinispan-spring4-embedded:jar:9.2.5.Final-redhat-1 missing from the Red Hat General Availability Maven repository.

Security fixes

Chapter 6. Known Spring Boot Issues

6.1. Known issues

  • SB-379: Missing APR/native library in the openshift-openjdk image.
  • SB-1413: Sources of the rx-java-2.2.4-redhat-00003 artifact missing from the Spring Boot 1.5.19.RELEASE release.

Chapter 7. Known issues affecting required infrastructure components

  • Fabric8 Maven Plugin Issue #1640: Pushing an image into a custom repository during an s2i build with FMP 4.1.0 results in a DuplicateKeyException.

    Affected components and component versions
    This issues affects Fabric8 Maven Plugin 4.1.0.
    Fabric8 Maven Plugin does not process ImageConfiguration unless ImageConfiguration also contains a BuildImageConfiguration. Without a recognizable BuildImageConfiguration, Fabric8 Maven Plugin repeatedly calls the s2i image generators to create another default ImageConfiguration that contains the expected BuildImageConfiguration. This results in more than one ImageConfiguration being specified for the given s2i build, which in turn results in a DuplicateKeyException when FMP attempts to push the image to the registry specified in the pom.xml configuration file. This leads to image build failures when a new image build is triggered by a change in the deployment configuration of a pod on OpenShift.

    To prevent Fabric8 Maven Plugin form generating a duplicate ImageConfiguration, place the image configuration inside a build section in the pom.xml configuration file of your project, as shown in the examples below. This in turn prevents the DuplicateKeyException when new image build is triggered by a change in the deployment configuration of the pod.


Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.