-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Do not use "star import" for org.apache.pulsar.functions.api.Record in order to be able to build Pulsar on JDK14+ #8370
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
- update Apache Parent Maven Pom to latest (upgrade plugins) - use explicit import for Record class (prevent clash with java.lang.Record)
|
I am trying to split the patch into smaller pieces because in #8360 integration tests and other CI jobs does not pass, probably due to the upgrade of the Maven Assembly plugin. @merlimat you already approved #8360, hopefully here the tests will pass without problem (otherwise we have serious issues on CI), PTAL and merge if you can. thanks in advance |
|
/pulsarbot rerun-failure-checks |
2 similar comments
|
/pulsarbot rerun-failure-checks |
|
/pulsarbot rerun-failure-checks |
|
I am seeing the same failure many times |
|
/pulsarbot rerun-failure-checks |
2 similar comments
|
/pulsarbot rerun-failure-checks |
|
/pulsarbot rerun-failure-checks |
|
I have sent a separate fix for the flaky test |
sijie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eolivelli the change looks good! But I think we should also consider enabling checkstyle across module to enforce consistent styles. There are some modules already running checkstyle. Are you interested in contributing code changes to enable them?
|
I had another change about upgrading checkstyle to latest version. |
…n order to be able to build Pulsar on JDK14+ (apache#8370) * Allow to build Pulsar on JDK14 - update Apache Parent Maven Pom to latest (upgrade plugins) - use explicit import for Record class (prevent clash with java.lang.Record) * xx * revert pom changes Co-authored-by: Enrico Olivelli <enrico.olivelli@diennea.com>
…n order to be able to build Pulsar on JDK14+ (apache#8370) * Allow to build Pulsar on JDK14 - update Apache Parent Maven Pom to latest (upgrade plugins) - use explicit import for Record class (prevent clash with java.lang.Record) * xx * revert pom changes Co-authored-by: Enrico Olivelli <enrico.olivelli@diennea.com>
Motivation
JDK14 introduced java.lang.Record, that is imported by default as "Record".
The build fails in some .java files due to the ambiguity between org.apache.pulsar.functions.api.Record and java.lang.Record.
Modifications
Use explicit imports instead of star import, only in the Java files that break the build.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.