-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-22927 Upgrade mockito version for Java 11 compatibility #584
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
2f0c20b to
ec04ec4
Compare
|
💔 -1 overall
This message was automatically generated. |
So the new mockito just drops the support for java 8? |
|
Comment on the similar issue raphw/byte-buddy#541 (comment). Work around for above can be to add module-info.class in . What do you think @Apache9?? |
|
Seems hadoop has already updated the mockito version to 2.23.4? And seems the UTs are fine so this maybe a too strict enforcer rule? @busbey PTAL. And why not upgrade to 2.28.2? And also there is a 3.0.0 release now? What's is the difference 3.x and 2.x? |
This sounded familiar so I dug about. This came up with a JRuby update on HBASE-20582 and is tracked in MENFORCER-300. On HBASE-20582 we pinned our version of JRuby to avoid the issue (which is what it looks like the byte-buddy developer suggested as a workaround). Since then MENFORCER-300 has been updated to include an example of how to ignore the |
|
Hadoop updating shouldn't be taken as an indicator of anything, IMHO. They only ensure a certain minimum JDK is used at build time; they don't have any checks to make sure generated artifacts will work with any particular JDK version. |
|
Checked out both HBASE-20582 and MENFORCER-300. Will follow the example of MENFORCER-300 and add module-info in ignoreclass section. |
|
💔 -1 overall
This message was automatically generated. |
65bdc75 to
64f8890
Compare
|
Still working on this @ravowlga123 ? |
No description provided.