Skip to Content
Product Information

New Versions of SAP Cloud SDK: 3.33.0 for Java and v45 for Continuous Delivery

Join us at TechEd

Gain some hands-on experience with SAP Cloud SDK. Together we will build a cloud-native application that connects to SAP S/4HANA Cloud. You will be the first to experience some brand new features and get support from the source of SAP Cloud SDK. Register for TechEd and add our session to your schedule.

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 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.33.0

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

Extensible destination loading

Destinations can be conveniently be added into the DestinationAccessor logic. It exposes two new methods appendDestinationLoader() and prependDestinationLoader() which add destination loaders with high or low priority to the accessor logic. Leverage a new default implementation for the DestinationLoader interface to load destinations created at runtime:

DestinationLoader loader = new DefaultDestinationLoader().registerDestination(myHttpDestination);
DestinationAccessor.appendDestinationLoader(loader);

Further improvements

The SCP Workflow API client library in module scp-workflow-cf is now generally available and released for productive usage.

In this release, we also improved and simplified the OData exceptions hierarchy, such as the subclasses of ODataException.

Several further improvements are listed in the full release notes.

Continuous Delivery Toolkit: Release Highlights v45

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

Deprecation of SAP Cloud SDK Pipeline

This is the last planned released of the SAP Cloud SDK Pipeline. In the last months the SAP Cloud SDK Pipeline and its features were merged into the General Purpose Pipeline of project “Piper” which will replace the SAP Cloud SDK Pipeline and should be used instead. The reasoning as well as further information how to adopt the General Purpose Pipeline are described in the guide.

You can find further details about the changes 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.33.0.

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.33.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-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.33.0.

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

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

Please also read this guide to learn how you can upgrade to the new General Purpose Pipeline.

Learn more about SAP Cloud SDK

Are you interested in details about a particular topic? Have a look at the SAP Cloud SDK documentation portal.

To ask a question or learn how others in the community use SAP Cloud SDK you can check out the Q&A place. Don’t 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.

/
1 Comment
You must be Logged on to comment or reply to a post.
  • Hi Team,

    I follow link to generate Neo app using SAP Cloud SDK with last release when i build it in my local

    mvn scp:clean scp:push -pl application -X

    I got some error:

    [DEBUG] Configuring mojo 'com.sap.cloud:neo-javaee7-wp-maven-plugin:1.86.9:run-console-command' with basic configurator -->
    [DEBUG]   (f) sdkInstallPath = D:\firstapp\application\scp\sdk-1.86.9
    [DEBUG]   (f) consoleCommand = start-local --shutdown-port 8003
    [DEBUG]   (f) consoleOutputPropertyDump = true
    [DEBUG]   (f) consoleRetryCount = 0
    [DEBUG]   (f) failOnError = true
    [DEBUG]   (f) mojoExecution = com.sap.cloud:neo-javaee7-wp-maven-plugin:1.86.9:run-console-command {execution: null}
    [DEBUG]   (f) project = MavenProject: com.sap.cmc.cloud:firstapp-application:1.0-SNAPSHOT @ D:\firstapp\application\pom.xml
    [DEBUG]   (f) relaxOnSdkVersion = false
    [DEBUG]   (f) skip = false
    [DEBUG]   (f) settings = org.apache.maven.execution.SettingsAdapter@1b7cae6f
    [DEBUG] -- end configuration --
    [DEBUG] Failed to check for plugin execution configuration parameter hint
    java.lang.NullPointerException
        at com.sap.core.sdk.cmd.mojo.AbstractConsoleCommandMojo.checkConfigurationForUnmappedParameters (AbstractConsoleCommandMojo.java:236)
        at com.sap.core.sdk.cmd.mojo.AbstractRunConsoleCommandMojo.checkConfiguration (AbstractRunConsoleCommandMojo.java:8327)
        at com.sap.core.sdk.cmd.mojo.AbstractRunConsoleCommandMojo.run (AbstractRunConsoleCommandMojo.java:1272)
        at com.sap.core.sdk.cmd.mojo.RunConsoleCommandMojo.execute (RunConsoleCommandMojo.java:22)
    

    and

    [ERROR] Failed to execute goal com.sap.cloud.sdk.plugins:scp-neo-maven-plugin:3.33.0:push (default-cli) on project firstapp-application: Command (start-local --shutdown-port 8003) return
    ed error code 1 (see above for more information). -> [Help 1]
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.sap.cloud.sdk.plugins:scp-neo-maven-plugin:3.33.0:push (default-cli) on project firstapp-application: C
    ommand (start-local --shutdown-port 8003) returned error code 1 (see above for more information).
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)