We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:
At the end of the article, you will find a set of instructions on how to update to the new versions.
Java Libraries: Release Highlights 3.25.0
You can update your dependencies of the SAP Cloud SDK for Java to version 3.25.0 and get the new version from Maven Central.
This version comes with some updates on the OData v4 support. Version identifiers are extracted from the ETag header in case of create and update operations. The result entities obtained via
ModificationRespnse.getResponseEntity() will also contain a version identifier. It will be sent as
IF-MATCH header in subsequent update and delete operations.
We introduced a new experimental method
ScpCfDestinationLoader.tryGetDestination() that allows custom request handling for resources of the SAP Cloud Platform Destination Service. HTTP interactions can be handled using the handler as functional interface.
String destinationName = getDestinationName();
String basePath = getBasePath();
String relativePath = getRelativePath();
Try<ScpCfDestination> destination = new ScpCfDestinationLoader()
destinationName, basePath, relativePath,
(uri) -> restTemplate.getForObject(uri, ScpCfDestinationServiceV1Response.class));
Several further improvements are listed in the full release notes.
We added support for collection type filter functions.
Also, some improvements in the OData client generator were made.
As usual, the full release notes contain a list of all improvements in this release.
We have also released version v39 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.
The latest release of our continuous delivery toolkit contains some changes related to unifying the pipeline configuration across the SAP technology landscape.
You can find the list of fixes and improvements in the complete release notes.
How to Update
To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:
- Open the pom.xml file in the root folder of your project.
- Locate the dependency management section and therein the
- Update the version of that dependency to
With this, you are already done thanks to the “bill of material” (BOM) approach. Your dependency should look like this:
<!-- possibly further managed dependencies ... -->
If you update from a version prior to 3.0.0, have a look at our migration guide.
If you are using the SAP Cloud SDK in a project of the SAP Cloud Application Programming Model, replace
sdk-modules-bom to only update the version of SDK modules, not further dependencies.
You can now recompile your project (be aware of the compatibility notes, though) and leverage the new features of the SAP Cloud SDK in version 3.25.0.
Of course, you can also generate a new project that uses version 3.25.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with
npm update in the root folder of your module. Note that this will also update other modules, unless you explicitly specify which packages to update. If you want to check beforehand what will change, use
Continuous Delivery Toolkit
If you are using the pipeline with a fixed version (as recommended since v7), update the continuous delivery toolkit with the following command, that you run on the server hosting the cx-server:
./cx-server update image
Learn more about SAP Cloud SDK
To learn how others in the community use SAP Cloud SDK you can check out more related blog posts.
Are you interested in a particular topic? It might be helpful to search the Q&A place? Feel free to ask your question there and do not forget to select the tag
SAP Cloud SDK.
If you are new to SAP Cloud SDK, get started and gain first hand-on exercise by following our tutorials.