Skip to content

CAP Java 5.x Migration Guide: removed repackaged Olingo #2528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eugene-andreev wants to merge 3 commits into
base: main
Choose a base branch
from
Open

CAP Java 5.x Migration Guide: removed repackaged Olingo #2528

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a4cfdb4
Removed repackaged Olingo Dependencies
eugene-andreev Apr 23, 2026
c02e6da
Update java/migration.md
eugene-andreev Apr 27, 2026
aeb7075
describe self repackage
eugene-andreev Apr 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions java/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,17 @@ The following table gives an overview about the removed properties:
- `com.sap.cds.services.ServiceExceptionUtils.getMessageTarget(String parameter, Class<E> type, Function<E, Object> path)` → `MessageTarget.create(parameter, type, path)`
- `com.sap.cds.services.ServiceExceptionUtils.getMessageTarget(String parameter, Function<StructuredType<?>, Object> path)` → `MessageTarget.create(parameter, path)`

### Removed repackaged Olingo Dependencies { #removed-olingo-4-to-5 }

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

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`
Copy link
Copy Markdown
Contributor

@BraunMatthias BraunMatthias Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the second sentence is not clear - it sounds like patching CAP libraries cds-adapter-odatav4 etc.

Copy link
Copy Markdown
Contributor Author

@eugene-andreev eugene-andreev Apr 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Described a bit more in details. We can even add the xml snippet from the our ex-library, or would it be too much?



## CAP Java 3.10 to CAP Java 4.0 { #three-to-four }

### New License
Expand Down
Loading