I continue to run into this problem. I know I saw this when I installed 2021-06 on Windows, but somehow I got to a point where having this override seemed like it was causing m2e to be unable to find classes that are clearly present in dependencies, and then when I removed these overrides, that seemed to fix the problem.
I'm now installing 2021-6 again, on an Ubuntu VM, and the build is reporting this error and not giving me any path to resolution, except for forcing the errors to be ignored. I wonder if after I force it to ignore in the workspace, whether it will then be perfectly happy if I then remove those overrides. No clue. I'm flying blind here. > -----Original Message----- > From: m2e-users-boun...@eclipse.org <m2e-users-boun...@eclipse.org> On > Behalf Of KARR, DAVID > Sent: Friday, December 18, 2020 9:44 AM > To: m2e-users@eclipse.org > Subject: [m2e-users] Getting "Plugin execution not covered" for maven- > compiler-plugin after upgrading from 2020-09 to 2020-12 > > I was previously using 2020-09, with most projects using: > * git > * springboot > * maven/m2e > * groovy plugin > > This was all working fine. > > I just installed 2020-12, with the same plugins I was using with 2020- > 09. I exported my preferences from my 2020-09 workspace and imported > them into my 2020-10 workspace. Using the same git repositories, I > imported two projects. When it finished compiling, I was left with the > following errors in both projects: > > * Plugin execution not covered by lifecycle configuration: > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (execution: > default-compile, phase: compile) > * Plugin execution not covered by lifecycle configuration: > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile > (execution: default-testCompile, phase: test-compile) > > In the past, I sometimes see this before I had installed all the > required m2e connectors. Now, when I go through "quick fix" on this, > then to "discover new m2e connectors", the only choices it gives me are > "Resolve Later", and the three variations of "Do not execute". I assume > choosing any of the latter would result in m2e not compiling code, so > that obviously won't work. > > I've checked the logs, and there is nothing relevant to this. > > What could I be missing? > > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > To unsubscribe from this list, visit > https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/m2e > -users__;!!BhdT!3QmrRTj4Ow0BdJVQU9OXHA1qQVSYJn0ILHzCJw2gEsA72Y7- > lLvBikdiK1A0Vw$ _______________________________________________ m2e-users mailing list m2e-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-users
