Remove legacy Cloudevent support#186
Merged
sophokles73 merged 2 commits intoeclipse-uprotocol:mainfrom Sep 3, 2025
Merged
Conversation
|
Code coverage report is ready! 📈
|
Also adapted USubscriptionClient to align with the latest specification.
532d256 to
bb39ca3
Compare
|
Code coverage report is ready! 📈
|
The existing classes for supporting the creation, mapping and validation of CloudEvents are not needed anymore because all uProtocol APIs use UMessage and UAttributes as parameter types. Application developers do not need to bother with CloudEvents anymore. Also bumped version to 3.0.0-SNAPSHOT Fixes eclipse-uprotocol#184
bb39ca3 to
b95acc9
Compare
|
Code coverage report is ready! 📈
|
PLeVasseur
approved these changes
Sep 1, 2025
PLeVasseur
left a comment
There was a problem hiding this comment.
Briefly looked through. Proforma approval.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The existing classes for supporting the creation, mapping and validation
of CloudEvents are not needed anymore because all uProtocol APIs use
UMessage and UAttributes as parameter types. Application developers
do not need to bother with CloudEvents anymore.
Addresses #184