-
Notifications
You must be signed in to change notification settings - Fork 908
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
[Build] Support property: maven.compiler.release for building BK with higher version JDK #4090
Conversation
… higher version JDK
rerun failure checks |
Failure is about maven-javadoc-plugin, but i didn't change it, seems to be not related? |
seems related, checking on local |
I could reproduce the CI failure on local, it is all about groovy, it could be fixed by removing "-T 1C" which indicates: can't run in parallel, don't know why.. I also tried upgrading to the latest groovy 3.0.19 for 3, it also failed unless i remove "-T 1C" any thought? |
Let me explain more about this PR. (I'm using JDK 17 to build on local) First of all, only with
|
Then from this issue: https://bugs.openjdk.org/browse/JDK-8193030, the last comment gives me a hint. In the meantime, I checked the maven-javadoc-plugin, as tag <packages> in <group> does the same thing, so I was double confirmed it is safe to be removed. |
After these two issues got fixed, here comes to the 3rd one:
As this answer suggests, that's why I added |
Final issue is this comment |
We are still using java8, we should keep the release.version to 8
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.
@Reidddddd Thanks for your contribution. But It seems contains some javadoc、constructor changes? I suggest to split them. And we are still supporting java8, I think we should keep release.version
to 8. WDYT?
@Reidddddd Closed by no update, feel free to reopen it if you still want to work on it. |
Motivation
With this feature, the compiler will detect and generate an error when using APIs that don't exist in previous releases of Java SE in advance.
Changes
Add property: maven.compiler.release
Master Issue: #4089