-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-28676 Make pre commit build for 3.x to only run jdk 17 test #6001
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -809,7 +809,7 @@ | |
| <tar.name>${project.build.finalName}.tar.gz</tar.name> | ||
| <maven.build.timestamp.format>yyyy-MM-dd'T'HH:mm</maven.build.timestamp.format> | ||
| <buildDate>${maven.build.timestamp}</buildDate> | ||
| <compileSource>1.8</compileSource> | ||
| <compileSource>17</compileSource> | ||
| <releaseTarget>8</releaseTarget> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What does it mean to have compile target at 17 but release target at 8? Can javac emit bytecode for 17 features for an 8 VM? We are dropping JDK8 runtime support, so I think we can move the release target up as well.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ReleaseTarget 17 will break mockito, need to dig more... |
||
| <!-- Build dependencies --> | ||
| <!-- The $revision feature is introduced in 3.5.0 --> | ||
|
|
||
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.
Big jump!