-
Notifications
You must be signed in to change notification settings - Fork 117
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
Quick-fix for failed maven mojo execution is not available since 2.2 #1292
Comments
@blacelle do you like trying to provide a PR for this? |
@laeubi I'm very sorry, but I feel I will not be able to contribute to m2e-core at the moment. I'm a 10+ years m2e happy user (even though early m2e-core days gave tough times to many users :)), and m2e-core is one of my main reason for sticking to Eclipse. The need for a dedicated IDE to contribute to m2e-core leads to a lot of friction on my side. (I already have multiple IDEs on my main computer, and working on multiple computers for different projects...). Also, I'm currently getting onboard to contribute to multiple additional OSS projects. Each new projects has its cost to get up-to-speed (and m2e-core cost is higher (seemingly due to Eclipse requirements)). If I may, I've been invited to give feedback around Equo IDE as a way to help contributing to another project: diffplug/spotless#1523 This approach may motive people like myself to contribute to m2e-core. (As a footline, this Quick-fix used to be available.) |
@blacelle I checked out the mentioned project but didn't see the error markers you mentioned, is there any steps to reperoduce this? |
#1291
I consider a multi-module project, with a maven-plugin configured.
https://github.com/solven-eu/cleanthat/blob/master/parent/pom.xml#L461
Since M2E - Maven Integration for Eclipse 2.2.0.20230228-2348 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e, some maven plugin executions are triggered (while previously not), and they are not as easy as before to be deactiveted: it used to be doable through the context menu:
The text was updated successfully, but these errors were encountered: