[data-plane]: Bump cloudevents.sdk.version from 2.0.0-milestone3 to 2.0.0-milestone4 in /data-plane

[dependabot]

Bumps cloudevents.sdk.version from 2.0.0-milestone3 to 2.0.0-milestone4.
Updates cloudevents-http-vertx from 2.0.0-milestone3 to 2.0.0-milestone4

Updates cloudevents-kafka from 2.0.0-milestone3 to 2.0.0-milestone4

Release notes

Sourced from cloudevents-kafka's releases.

2.0.0 Milestone 4

On the behalf of the CloudEvents community, I'm pleased to announce that we're releasing a new 2.0.0 milestone.

In this release we dealt with the outstanding issue of representing the CloudEvent data field. After a lot of discussions and proposals, we reached an agreement on this interface:

public interface CloudEventData {
    byte[] toBytes();
}

And now CloudEvent#getData() returns CloudEventData. This additional indirection doesn't change the assumptions of the original interface, but allows extensibility and optimizations, without reimplementing/wrapping the CloudEvent interface. We also implemented, in the jackson module, an optimization to read/write CloudEvent with json values in it and we provide a new interface, when deserializing events, to map the CloudEventData to any custom implementation.

You can check out all the changes here: https://github.com/cloudevents/sdk-java/milestone/4?closed=1

To start using it, look at the documentation on the official website: https://cloudevents.github.io/sdk-java/

What's next

If you want to contribute, feel free to pick any good first issue here: https://github.com/cloudevents/sdk-java/labels/good%20first%20issue

If you want to join the discussions about new features and how to improve the existing ones, feel free to look on issues and pr with discussion label: https://github.com/cloudevents/sdk-java/labels/discussion

As all milestones, this is a preview of the library for the community, nothing is written on the stone, so please give us feedback in order to improve this project!

Happy hacking!

Commits

• f52356e Bump to 2.0.0-milestone4 (#254)
• de2052c CloudEventDataMapper (#252)
• 5e747e7 Introduce JsonCloudEventData (#251)
• f9e31ef Introduce CloudEventData (#250)
• a09b03b Serialize time to RFC3339 compliant string (#249)
• f219b69 Release process docs (#248)
• 3cea024 Bump to 2.0.0-SNAPSHOT (#247)
• See full diff in compare view

Updates cloudevents-json-jackson from 2.0.0-milestone3 to 2.0.0-milestone4

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)