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

Lower severity of m2e's 'Project configuration is not up-to-date...' diagnostics #774

Merged
merged 1 commit into from
Aug 29, 2018

Conversation

snjeza
Copy link
Contributor

@snjeza snjeza commented Aug 28, 2018

Fixes #763

Signed-off-by: Snjezana Peco [email protected]

@snjeza snjeza requested review from gorkem and fbricon August 28, 2018 16:49
String message = marker.getAttribute(IMarker.MESSAGE, "");
if (message != null && message.startsWith("Project configuration is not up-to-date with pom.xml.")) {
message = "Project configuration is not up-to-date with pom.xml, requires an update.";
d.setSeverity(DiagnosticSeverity.Warning);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No the severity change should be at the m2e preferences level, or else the build command will continue to fail if such an error is reported. See microsoft/vscode-java-debug#358

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have updated the PR.

@@ -148,6 +151,12 @@ public void start(BundleContext bundleContext) throws Exception {
contentProviderManager = new ContentProviderManager(preferenceManager);
logInfo(getClass() + " is started");
configureProxy();
configureMavenPreferences();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be moved to the preferences manager

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

initializeJDTOptions should be removed BTW, since it's covered by PreferenceManager.initialize()

configureMavenPreferences();
}

private void configureMavenPreferences() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have removed it.

@fbricon
Copy link
Contributor

fbricon commented Aug 29, 2018

test this please

@fbricon fbricon merged commit 29dc698 into eclipse-jdtls:master Aug 29, 2018
@snjeza snjeza deleted the issue-763 branch August 29, 2018 22:03
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.

2 participants