You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, simply check the compilation options may have some issue for some cases, An example is the project in the linked issue.
User can set the source level to 17, and target level to 8. Meanwhile, use [--release, 8] as the compilation arguments. Normally, this should fail during compilation. But the project uses a annotation processor to make it work.
Which says, maybe we should just simply get the source compatibility from the property, not infer it from the compilation options?
Full context can be found here: redhat-developer/vscode-java#3721
In short, simply check the compilation options may have some issue for some cases, An example is the project in the linked issue.
User can set the source level to 17, and target level to 8. Meanwhile, use [
--release
,8
] as the compilation arguments. Normally, this should fail during compilation. But the project uses a annotation processor to make it work.Which says, maybe we should just simply get the source compatibility from the property, not infer it from the compilation options?
@Arthurm1, WDYT?
The text was updated successfully, but these errors were encountered: