Skip to content

Set default severity of "Circular classpath" to warning #2170

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

Merged
merged 2 commits into from
Jul 22, 2022

Conversation

CsCherrYY
Copy link
Contributor

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

This is a workaround about redhat-developer/vscode-java#718, eclipse-buildship/buildship#460

We observed a lot of projects (especially Gradle projects) have this error. Actually, we have a workaround to set the severity to warning manually: eclipse-buildship/buildship#460 (comment)

But for VS Code users, there is no existing wizard to config this setting and it's also hard and not recommended to change .prefs file in .settings folder. In this way, we can make the default value of config to warning to make the users not be blocked by this error at least.

For example, given a sample project https://github.com/opensearch-project/OpenSearch.git, the redhat.java extension reports circular dependency found in the project and the project can't be built. If we set this severity to warning, we can only find some errors in RestTestFromSnippetsTaskTests.java (due to Java/Groovy polyglot project, which is not supported yet) and the project can be built.

@rgrunber
Copy link
Contributor

rgrunber commented Jul 22, 2022

Setting to warning seems reasonable. I would just add it to some of the test cases in JavaSettingsTest.java . On second thought, this is fine. The tesing of JavaCore.COMPILER_PB_MISSING_SERIAL_VERSION should cover this.

@rgrunber rgrunber merged commit dc6b08c into eclipse-jdtls:master Jul 22, 2022
@CsCherrYY CsCherrYY deleted the cs-circular-dependency branch July 25, 2022 01:39
@rgrunber rgrunber added this to the End August 2022 milestone Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants