-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Allow building Apache Pulsar on JDK15+ - upgrade Maven Assembly Plugin #8360
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.
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
Conversation
@eolivelli I believe #8361 fixes the grpc version issues in master branch. I cherry picked the commit to another PR that I'm working to test it. #8362 is the reason why master branch got into a broken state. |
|
Good to know. |
|
/pulsarbot run-failure-checks |
- update Apache Maven Assembly Plugin - use explicit import for Record class (prevent clash with java.lang.Record)
ec70fa2 to
fdc3cd2
Compare
|
rebased onto current master, let's see CI again |
|
@lhotari test failed with this error probably your fix #8386 will help |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
One job fails with |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
apache#8360) Motivation Currently Pulsar does not build on JDK15 Modifications update Maven Assembly plugin move maven-git-commit-id plugin execution only inside Pulsar Common (in order to speed up the build) upgrading the Maven Assembly Plugin resulted in a different output for the "binaries", I had to update license files forced version of Jersey to 2.31 in "Presto" distribution (otherwise the license check failed, because it does not handle different versions between main pulsar binaries and presto distribution inside lib/presto/lib, and this makes sense to me) Verifying this change This change is already covered by existing tests * Allow to build Pulsar on JDK14+ - update Apache Maven Assembly Plugin - use explicit import for Record class (prevent clash with java.lang.Record) * revert Apache pom update * fix * Fix presto distribution - due to maven assembly plugin upgrade * fix licenses * Fix kafka clients * fix LICENSE Co-authored-by: Enrico Olivelli <enrico.olivelli@diennea.com> Co-authored-by: Enrico Olivelli <eolivelli@apache.org>
apache#8360) Motivation Currently Pulsar does not build on JDK15 Modifications update Maven Assembly plugin move maven-git-commit-id plugin execution only inside Pulsar Common (in order to speed up the build) upgrading the Maven Assembly Plugin resulted in a different output for the "binaries", I had to update license files forced version of Jersey to 2.31 in "Presto" distribution (otherwise the license check failed, because it does not handle different versions between main pulsar binaries and presto distribution inside lib/presto/lib, and this makes sense to me) Verifying this change This change is already covered by existing tests * Allow to build Pulsar on JDK14+ - update Apache Maven Assembly Plugin - use explicit import for Record class (prevent clash with java.lang.Record) * revert Apache pom update * fix * Fix presto distribution - due to maven assembly plugin upgrade * fix licenses * Fix kafka clients * fix LICENSE Co-authored-by: Enrico Olivelli <enrico.olivelli@diennea.com> Co-authored-by: Enrico Olivelli <eolivelli@apache.org>
Motivation
Currently Pulsar does not build on JDK15
Modifications
Verifying this change
This change is already covered by existing tests