-
Notifications
You must be signed in to change notification settings - Fork 135
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
Baseline applies the -parameters
javac option for method parameter metadata
#1690
Conversation
Generate changelog in
|
…metadata This produces bytecode with method paramter metadata to support more powerful reflection features and stronger error-prone automated migrations.
5404e90
to
0ceb2b6
Compare
project.getTasks() | ||
.withType(JavaCompile.class) | ||
.configureEach(javaCompileTask -> | ||
javaCompileTask.getOptions().getCompilerArgs().add("-parameters")); |
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.
I looked to see if there was any downsides of doing this and found these: https://stackoverflow.com/a/44075684/139766. None of them seem that bad.
👍 |
Released 3.75.0 |
Before this PR
No parameter metadata.
After this PR
This produces bytecode with method parameter metadata to support
more powerful reflection features and stronger automated migrations.
==COMMIT_MSG==
Baseline applies the
-parameters
javac option for method parameter metadata==COMMIT_MSG==
Possible downsides?
Not sure how to test this. The change is pretty simple though, and we don't need to worry about applying the
-parameters
option twice becausejavac
doesn't mind.