Uh oh!
There was an error while loading. Please reload this page.
HBASE-28676 Make pre commit build for 3.x to only run jdk 17 test - #6001
Conversation
Apache-HBase
commented
Jun 19, 2024
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 19, 2024
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 19, 2024
💔 -1 overall
This message was automatically generated. |
Apache9
commented
Jun 19, 2024
Filed HBASE-28679 for the xml problem, and we can not move releaseTarget to 17 because there are tests failures on mockito, which may require code change. Plan to solve it in HBASE-28675. |
Apache-HBase
commented
Jun 19, 2024
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 22, 2024
💔 -1 overall
This message was automatically generated. |
Apache9
commented
Jun 22, 2024
The error for compile for the current master branch is expected, since we change to use jdk17 for compiling, we need to add some compile args for error prone. |
Apache-HBase
commented
Jun 22, 2024
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 23, 2024
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 23, 2024
🎊 +1 overall
This message was automatically generated. |
Apache9
commented
Jun 24, 2024
OK, good. Xml check can pass now. |
Apache9
commented
Jun 24, 2024
Merging this will cause the nightly build for master and branch-3 to fail since we still use jdk11 for general checks. Will start to work on HBASE-28678 ASAP after merging this PR. |
| <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> |
| <buildDate>${maven.build.timestamp}</buildDate> | ||
| <compileSource>1.8</compileSource> | ||
| <compileSource>17</compileSource> | ||
| <releaseTarget>8</releaseTarget> |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
ReleaseTarget 17 will break mockito, need to dig more...
Apache9
commented
Jun 26, 2024
@ndimiduk See here, I tried to jump to 17 too for releaseTarget at first, but it breaks mockito, so I plan to address it in HBASE-28675 since it may require java code changes. |
) Signed-off-by: Nick Dimiduk <ndimiduk@apache.org> (cherry picked from commit 80516d7)
ndimiduk
commented
Jun 27, 2024
Makes sense. Thanks @Apache9 ! |
…ache#6001) Signed-off-by: Nick Dimiduk <ndimiduk@apache.org>
No description provided.