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.10.0
- Java libraries in version 2.25.0
- Continuous delivery toolkit in version v27
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.10.0
You can update your dependencies of the SAP Cloud SDK for Java to version 3.10.0 and consume the new version from Maven Central.
The latest version updates several dependencies including the dependency to SAP Cloud Application Programming Model Java libraries, resolving a circular dependency issue. This also makes it easier to update to SDK version 3 in CAP projects.
This release includes the fix for an issue with HTTP destinations on Cloud Foundry where the default JDK trust store was mistakenly taken into account even if an own trust store is defined.
We’ve resolved an issue with OData query formatting for filter expressions with date and time values. This affects queries comparing entity properties based on
Java Libraries: Release Highlights 2.25.0
For a complete view on what has changed, take a look at the full release notes.
We fixed an issue with cached destinations, where the retrieving of certificates, additional OAuth tokens, and proxy configurations was not working correctly.
The default path for the
service-mapping.json file in the VDM generator was corrected. This fixes an issue on Windows systems where a hard coded
/ led to a failure.
As usual, the full release notes contain a list of all improvements in this release.
Continuous Delivery Toolkit: Release Highlights v27
We have also released version v27 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.
Multi-Target Applications (MTA) can now make use of the new Cloud MTA Build Tool. In version v27 the classic (Java-based) MTA Builder is still the default option. You can change the used tool as documented. In one of our next releases, we plan to switch the default to the new build tool.
We’ve added frontend integration tests support for Maven projects, as it was already possible for Node.js projects. The pipeline will run the
ci-it-frontend script from your
package.json, if one is provided.
Starting from this version all pipeline stages have access to the application’s source code. Previously this was not always possible due to Jenkins pipeline internals.
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.10.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.10.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