-
Notifications
You must be signed in to change notification settings - Fork 31
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
Check that pom.xml and MANIFEST.MF have same version #165
Comments
I think we can try to improve that deeper in tycho, by making the validate-version mojo m2e compatible so it would be run by default by m2e on build, and would report errors "naturally". |
I'm fine with Eclipse only. Only question is can we get quick fix that way too? |
It seems that code action's (quick fixes) can be contributed through LemMinX extensions. Perhaps when a tycho build error is reported, it could populate the list of quick fixes, and if the build error from tycho reports an incorrect pom version, a quick fix could be contributed to fix this. I haven't thought too much about the implementation details, but this seems possible. |
It requires more investigation, but for any marker in Eclipse IDE, it's possible to get a quickfix easily enough. The tricky part remains about making Maven show a marker for the Tycho validate-version mojo. Given that Tycho is a Maven extension (although this specific mojo may not need it), it might be tricky to get and a plain text approach in the LS may be more profitable in the end. |
Wouldn't such Tycho and therefore also PDE specific feature be better placed in the It already builds the bridge from the bnd-maven-plugin and Felix' maven-bundle-plugin and also handles Tycho plugins. |
It's tycho specific but it's not intrusive and will help everyone using Tycho.
https://git.eclipse.org/c/platform/eclipse.platform.releng.git/tree/bundles/org.eclipse.releng.tools/src/org/eclipse/releng/internal/tools/pomversion/PomVersionErrorReporter.java has implementation that's purely eclipse specific.
The text was updated successfully, but these errors were encountered: