Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:

In this blog post, we will walk you through the highlights of these releases. For a complete overview, visit our release notes for the Java libraries, for the JavaScript libraries, and for the continuous delivery toolkit. The release notes also include the change log of all our releases so far.
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.18.0

You can update your dependencies of the SAP Cloud SDK for Java to version 3.18.0 and consume the new version from Maven Central.

In this release, the beta annotated CustomOperationRequestBuilder class has been renamed to FunctionRequestBuilder.

Version 3.18.0 also contains a fix for an issue with the access token validation in a provider/subscriber setup, when having multiple XSUAA service bindings, e.g. one with service plan broker and one with service plan application.

For simplicity reasons, the custom pmd plugin was removed. Starting with this version, the ruleset contains only the rules shipped with the SAP Cloud SDK. All other imported rules were removed. To keep using the ruleset with the standard pmd plugin, for example with SAP Cloud SDK for Continuous Delivery, we recommend adding the following configuration to the root pom.xml of your project:

Further improvements

Several further improvements are listed in the full release notes.

Continuous Delivery Toolkit: Release Highlights v32

We have also released version v32 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.

A custom linting script named ci-lint is executed as part of the Lint stage if it is defined in the scripts section of the package.json file. In the absence of this script, the Lint stage now also supports non-SAPUI5 Javascript/Typescript projects by executing ESLint with a provided default configuration. See the documentation for more details.

The Artifact Deployment stage can now also deploy npm build artifacts. It uploads everything that is not excluded in .npmignore via the command npm publish. Also, the requirements for Maven projects have been relaxed so that any multi-module projects are now supported. See the documentation for more details.

Further improvements

You can find further fixes and improvements in the complete release notes.

How to Update

Java libraries

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 sdk-bom dependency.

  • Update the version of that dependency to 3.18.0.

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-bom with 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.18.0.

Of course, you can also generate a new project that uses version 3.18.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with -DarchetypeVersion=3.18.0 (or RELEASE).

JavaScript libraries

To update the version of the SAP Cloud SDK JavaScript libraries used in an existing project, use the command 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 npm outdated.

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.