We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:
- Java libraries in version 3.21.0
- Continuous delivery toolkit in version v34
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.21.0
You can update your dependencies of the SAP Cloud SDK for Java to version 3.21.0 and get the new version from Maven Central.
In this version, we enhanced the interface
CloudPlatform with the method
setEnvironmentVariableReader(Function<String, String>) allowing adjustments in the way how environment variables are read.
We added experimental filter expressions in the OData client value types of package
com.sap.cloud.sdk.datamodel.odata.client.expression allowing custom requests to have entity-independent, yet type-safe query filters.
Several further improvements are listed in the full release notes.
OData clients generated with SDK version 1.21.1 yield more narrow types on the
_allFields properties, that differ from older generated clients. Old clients are still supported but will be deprecated soon.
The Internal directory structure has changed. This might be a breaking change for users that reference internal modules directly.
Experimental OData v4 Support
This release of SAP Cloud SDK adds experimental support for OData v4. Details will follow in a separate blog post. Note that functionality related to OData v4 is subject to change.
As usual, the full release notes contain a list of all improvements in this release.
Continuous Delivery Toolkit: Release Highlights v34
We have also released version v34 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.
In this release, development dependencies are excluded from the npm audit.
The Multi-target applicartion (MTA) build process is now able to read the correct configured npm registry without the need for
You can find further 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:
<dependencyManagement> <dependencies> <dependency> <groupId>com.sap.cloud.sdk</groupId> <artifactId>sdk-bom</artifactId> <version>3.21.0</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> <!-- possibly further managed dependencies ... --> </dependencyManagement>
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.21.0.
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.