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 #763

Closed
fbricon opened this issue Aug 22, 2018 · 0 comments
Closed

Comments

@fbricon
Copy link
Contributor

fbricon commented Aug 22, 2018

Currently, the build command fails whenever the Project configuration is not up-to-date with pom.xml. Select: Maven->Update Project... from the project context menu or use Quick Fix. problem is reported on a Maven project.
We have 2 issues here:

  • First of all, the severity should be downgraded to warning in the server preferences, as it's rarely an actual error
  • The message itself is completely Eclipse-UI bound, thus irrelevant to other clients. It should be overridden and reported to clients as Project configuration is not up-to-date with pom.xml, requires an update. (a better message will be accepted).

See microsoft/vscode-java-debug#358 and redhat-developer/vscode-java#608

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

No branches or pull requests

2 participants