From a4cfdb4075cea442fbf25659649c5fc1add27dd1 Mon Sep 17 00:00:00 2001 From: Evgeny Andreev Date: Thu, 23 Apr 2026 10:50:49 +0200 Subject: [PATCH 1/4] Removed repackaged Olingo Dependencies --- java/migration.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/java/migration.md b/java/migration.md index 8bb6eeacf..082cf2e7d 100644 --- a/java/migration.md +++ b/java/migration.md @@ -109,6 +109,17 @@ The following table gives an overview about the removed properties: - `com.sap.cds.services.ServiceExceptionUtils.getMessageTarget(String parameter, Class type, Function path)` → `MessageTarget.create(parameter, type, path)` - `com.sap.cds.services.ServiceExceptionUtils.getMessageTarget(String parameter, Function, Object> path)` → `MessageTarget.create(parameter, path)` +### Removed repackaged Olingo Dependencies { #removed-olingo-4-to-5 } + +The internal `mvn` modules `repackaged/odata-v4-lib` and `repackaged/odata-v2-lib` are removed and not released anymore. If the project directly referenced those modules and doesn't compile after migrating to CAP Java 5.x, there are 3 options to keep the compatability of the code base. + +1. [**Recommended**] Remove `mvn` dependencies to `repackaged/odata-v4-lib`, `repackaged/odata-v2-lib` and rewrite code using CAP Java native APIs + +2. Self-repackage and reuse the Olingo modules with `maven-dependency-plugin` + +3. Use upstream open-source Apache Olingo. Change dependencies from corresponding internal CAP `mvn` modules to OSS `org.apache.olingo:olingo-odata4`, `org.apache.olingo:olingo-odata2` + + ## CAP Java 3.10 to CAP Java 4.0 { #three-to-four } ### New License From c02e6da37f3e3985393fc46975f90360b1ace36a Mon Sep 17 00:00:00 2001 From: Evgeny Andreev Date: Mon, 27 Apr 2026 09:02:44 +0200 Subject: [PATCH 2/4] Update java/migration.md Co-authored-by: BraunMatthias <59841349+BraunMatthias@users.noreply.github.com> --- java/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/migration.md b/java/migration.md index 082cf2e7d..6d7d8fc11 100644 --- a/java/migration.md +++ b/java/migration.md @@ -111,7 +111,7 @@ The following table gives an overview about the removed properties: ### Removed repackaged Olingo Dependencies { #removed-olingo-4-to-5 } -The internal `mvn` modules `repackaged/odata-v4-lib` and `repackaged/odata-v2-lib` are removed and not released anymore. If the project directly referenced those modules and doesn't compile after migrating to CAP Java 5.x, there are 3 options to keep the compatability of the code base. +The internally used maven modules `repackaged/odata-v4-lib` and `repackaged/odata-v2-lib` are removed from the delivery. If the project directly references these modules and doesn't compile after migrating to CAP Java 5.x, there are 3 options to keep the compatibility of the code base: 1. [**Recommended**] Remove `mvn` dependencies to `repackaged/odata-v4-lib`, `repackaged/odata-v2-lib` and rewrite code using CAP Java native APIs From aeb7075d8ba549bd8d3d995285a9121da6e7ce59 Mon Sep 17 00:00:00 2001 From: Evgeny Andreev Date: Mon, 27 Apr 2026 09:13:04 +0200 Subject: [PATCH 3/4] describe self repackage --- java/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/migration.md b/java/migration.md index 6d7d8fc11..d9528dfb4 100644 --- a/java/migration.md +++ b/java/migration.md @@ -115,7 +115,7 @@ The internally used maven modules `repackaged/odata-v4-lib` and `repackaged/odat 1. [**Recommended**] Remove `mvn` dependencies to `repackaged/odata-v4-lib`, `repackaged/odata-v2-lib` and rewrite code using CAP Java native APIs -2. Self-repackage and reuse the Olingo modules with `maven-dependency-plugin` +2. Use the Maven Dependency Plugin `maven-dependency-plugin` for unpacking (extracting contents of dependency) Olingo sources into your code base during the project build 3. Use upstream open-source Apache Olingo. Change dependencies from corresponding internal CAP `mvn` modules to OSS `org.apache.olingo:olingo-odata4`, `org.apache.olingo:olingo-odata2` From 64fb18ae8af5c986acc38de7abd7ebcf44fe5c81 Mon Sep 17 00:00:00 2001 From: Mahati Shankar <93712176+smahati@users.noreply.github.com> Date: Tue, 28 Apr 2026 14:22:28 +0200 Subject: [PATCH 4/4] cosmetics --- java/migration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/java/migration.md b/java/migration.md index e1c9297dd..8d7cf5f61 100644 --- a/java/migration.md +++ b/java/migration.md @@ -142,11 +142,11 @@ None The internally used maven modules `repackaged/odata-v4-lib` and `repackaged/odata-v2-lib` are removed from the delivery. If the project directly references these modules and doesn't compile after migrating to CAP Java 5.x, there are 3 options to keep the compatibility of the code base: -1. [**Recommended**] Remove `mvn` dependencies to `repackaged/odata-v4-lib`, `repackaged/odata-v2-lib` and rewrite code using CAP Java native APIs +1. [**Recommended**] Remove `mvn` dependencies to `repackaged/odata-v4-lib`, `repackaged/odata-v2-lib`, and rewrite code using CAP Java native APIs. -2. Use the Maven Dependency Plugin `maven-dependency-plugin` for unpacking (extracting contents of dependency) Olingo sources into your code base during the project build +2. Use `maven-dependency-plugin` to unpack (extract contents of dependency) Olingo sources into your code base during the project build. -3. Use upstream open-source Apache Olingo. Change dependencies from corresponding internal CAP `mvn` modules to OSS `org.apache.olingo:olingo-odata4`, `org.apache.olingo:olingo-odata2` +3. Use upstream open-source Apache Olingo. Change dependencies from corresponding internal CAP `mvn` modules to OSS packages `org.apache.olingo:olingo-odata4`, `org.apache.olingo:olingo-odata2` ## CAP Java 3.10 to CAP Java 4.0 { #three-to-four }