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

Quick-fix for failed maven mojo execution is not available since 2.2 #1292

Open
blacelle opened this issue Mar 3, 2023 · 3 comments
Open

Comments

@blacelle
Copy link

blacelle commented Mar 3, 2023

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

image

@laeubi
Copy link
Member

laeubi commented Mar 8, 2023

@blacelle do you like trying to provide a PR for this?
I think the main work would here to enable a quickfix, extract the required data and then you can use the code that is used as a quickfix when you open if from the pom:

grafik

@blacelle
Copy link
Author

blacelle commented Mar 8, 2023

@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.)
(As a second footline, some other issues/features may have more appealing to myself (e.g. like optimizing m2e-core over large multi-module projects). (I've not been able to find it back, but I remember @mickaelistria suggesting (quite some time ago) room for improvment by processing/resolveing multiple modules in one-pass, instead of on a per-module basis). I kept it in mind since then.)

@laeubi
Copy link
Member

laeubi commented Jun 26, 2023

@blacelle I checked out the mentioned project but didn't see the error markers you mentioned, is there any steps to reperoduce this?

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

No branches or pull requests

2 participants