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

Fix lifecycle mapping metadata #69

Merged
merged 1 commit into from
Apr 23, 2022
Merged

Fix lifecycle mapping metadata #69

merged 1 commit into from
Apr 23, 2022

Conversation

KengoTODA
Copy link
Member

I've fixed <goal> in META-INF/m2e/lifecycle-mapping-metadata.xml, however this fix isn't enough to run SpotBugs from m2e. I've installed 3.1.6-SNAPSHOT in local, and confirmed that its goal is linked with lifecycle:

screenshot from 2018-07-02 09-31-56

But even when I clean the Eclipse project, it won't run SpotBugs. At least, I found nothing in in progress bar, and no report founds in target directory.

@KengoTODA KengoTODA self-assigned this Jul 2, 2018
@KengoTODA KengoTODA requested a review from hazendaz July 2, 2018 01:42
@hazendaz
Copy link
Member

hazendaz commented Jul 2, 2018

https://stackoverflow.com/questions/30596850/how-to-combine-the-update-of-a-m2e-maven-project-in-eclipse-with-a-maven-build

It appears because the 'check' is in the VERIFY phase, a package will need run so eclipse is not going to do anything past compile. I think if you test again changing that phase for the test to compile you are likely to get it working. Then the question is, do we want that in the compile phase?

@KengoTODA
Copy link
Member Author

I think compile phase isn't good. At least, currently SpotBugs doesn't support incremental analysis, then analysis on compile phase should make development experience really bad.

@e-shreve-ti
Copy link

Any chance this fix can be finished? Looks like a test was failing against the change, but that the test needs to be updated. Would be nice to have this fix build in rather than requiring users to specify the correct lifecycle management setting themselves.

@hazendaz
Copy link
Member

@e-shreve-ti Would this solve your issue -> here They are supporting spotbugs now with m2e integration.

@e-shreve-ti
Copy link

Sorry. PEBCAK. I knew of m2e-code-quality but missed that they had multiple features and had only installed their checkstyle feature.

@hazendaz
Copy link
Member

@KengoTODA Can you rebase this and get working what you did? While it doesn't fix everything, if I recall it was useful and with now m2e-code-quality already working with us, we may not yet need a full solution. We probably could leverage what they have done and/or just drop this entirely and point users to their support.

@hazendaz
Copy link
Member

merging, will add missing spotbugs and new verify goals separately. Also looking at m2e-code -quality to see about just introducing that code directly.

@hazendaz hazendaz merged commit 3bc9a68 into spotbugs Apr 23, 2022
@hazendaz hazendaz deleted the close-68 branch April 23, 2022 14:30
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.

None yet

3 participants