Skip to content
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

Do not forget existing project options when setting null analysis options #2299

Merged
merged 1 commit into from
Oct 28, 2022

Conversation

CsCherrYY
Copy link
Contributor

@CsCherrYY CsCherrYY commented Oct 28, 2022

Signed-off-by: Shi Chen [email protected]

fix redhat-developer/vscode-java#2764

IJavaProject.setOptions() will replace existing options with default values if not exist in the map, so the source level information will be lost after we set null analysis options.

Sets the project custom options. All and only the options explicitly included in the given table are remembered; all previous option settings are forgotten, including ones not explicitly mentioned.

We should merge the non-inherit project options before setting it.

@CsCherrYY CsCherrYY added the bug label Oct 28, 2022
@jdneo
Copy link
Contributor

jdneo commented Oct 28, 2022

Maybe considering add some test cases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

source level preferences are ignored when the project compliance is different from configured JDK
3 participants