Skip to content

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

Merged
smahati merged 5 commits into
mainfrom
java-olingo-migration
Apr 28, 2026
Merged

CAP Java 5.x Migration Guide: removed repackaged Olingo#2528
smahati merged 5 commits into
mainfrom
java-olingo-migration

Conversation

@eugene-andreev

Copy link
Copy Markdown
Contributor

No description provided.

Comment thread java/migration.md Outdated
Comment thread java/migration.md Outdated

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`

Copy link
Copy Markdown
Contributor

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

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?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ah ok, got it

eugene-andreev and others added 2 commits April 27, 2026 09:02
Co-authored-by: BraunMatthias <59841349+BraunMatthias@users.noreply.github.com>
@smahati
smahati merged commit 95c6479 into main Apr 28, 2026
7 checks passed
@smahati
smahati deleted the java-olingo-migration branch April 28, 2026 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants