RHOAR Spring Boot 1.5.x Release Notes
For use with 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.
Fabric8 Maven Plugin
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
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:
- For a list of technologies that are supported for integration with RHOAR Spring Boot in production environments see the Supported Spring Boot configurations and integrations.
- For a list of RHOAR Spring Boot 1.5.x runtime artifacts and their versions see the Spring Boot 1.5.19.RELEASE component details page.
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:
org.infinispan:infinispan-spring4-embedded:jar:9.2.5.Final-redhat-1missing from the Red Hat General Availability Maven repository.
Chapter 6. Known Spring Boot Issues
6.1. Known issues
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
- Affected components and component versions
- This issues affects Fabric8 Maven Plugin 4.1.0.
Fabric8 Maven Plugin does not process
ImageConfigurationalso contains a
BuildImageConfiguration. Without a recognizable
BuildImageConfiguration, Fabric8 Maven Plugin repeatedly calls the s2i image generators to create another default
ImageConfigurationthat contains the expected
BuildImageConfiguration. This results in more than one
ImageConfigurationbeing specified for the given s2i build, which in turn results in a
DuplicateKeyExceptionwhen FMP attempts to push the image to the registry specified in the
pom.xmlconfiguration 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
buildsection in the
pom.xmlconfiguration file of your project, as shown in the examples below. This in turn prevents the
DuplicateKeyExceptionwhen new image build is triggered by a change in the deployment configuration of the pod.
<configuration> <images> <image> <name> artifactrepository.somecompany.com:18444/demo-boot/demo-boot:1.0 </name> <build> <from> fabric8/S2I_BASE_IMAGE_NAME </from> <assembly> <basedir> /deployments </basedir> <descriptorRef> artifact-with-dependencies </descriptorRef> </assembly> <env> <JAVA_LIB_DIR> /deployments </JAVA_LIB_DIR> <JAVA_MAIN_CLASS> org.example.class.name.Main </JAVA_MAIN_CLASS> </env> </build> ... </image> </images> ... </configurtation>