Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Getting "Plugin execution not covered" for maven-compiler-plugin after upgrading from 2020-09 to 2020-12
  • From: "KARR, DAVID" <dk068x@xxxxxxx>
  • Date: Tue, 29 Jun 2021 20:18:31 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OPdbsBnZq6lZs23XL2guAWKYry6j1AmrKmkXWrQ+XYg=; b=eoRA44PpdrMSrRy/REX4liMGkxN9xYs8S6fWdPhyISe33BqBUNO+wY2NOgA6GAVO/Q6Yclxsis8nbFhtyiuefoNLsRruFu3qC8ivClp43bhrQUWvNYIWT+gVT+4my0WkQNDmeEcGJmldw4nvvXwYwPPAs3TscB+E0OiZQ1C/slzeio5gcCJDXmZ8NFVPrGqokUR57lvopwKhNnZ76BkhLfoBgTDtws8qFGiRwkamPS3CivaAUcFtOACz7ZXLraqNCWTXdbFmgyoHuFJsy8WxTb2C9r1/Q52mktnwSb7z2V0tir2SI3H47oB5qgmc73/xD3+020W+qeVbSGd8KykiBQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=gUhin+JTUqR3aHc8508rIkQ/+0GYDYLrEl3qTFGMumzAa8NfNtyDOsXlMIUr8AuELJhr/hNyrLGn7eut3m4+ZsbUSKfolJ1G9Y7+0HlEQTLtNgum3G5/HbsBeVB95MirgeuTXJmKseU5gpZciB3aaIKg3rpYSR6708kCQzj8a7BmkmFHKL8mYjJrCDsjkWKgcBIvz33LJSzdIitHgMk00b4Yo8CirIAs2PKdgV1QEZx3FwfNSnRl43luYeFTQCuCeWGLYCRUMvDtfTtfNmQGHGFqbYkRWrqIQHmuNv5vzrm+8+0th9z/snAazzSRFNXs/Swb5nPpFeLemUpzZwP4Sg==
  • Delivered-to: m2e-users@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AdbVXWJ+WhE5hxT5Q/ayTeyofFxwryXxgp9A
  • Thread-topic: [m2e-users] Getting "Plugin execution not covered" for maven-compiler-plugin after upgrading from 2020-09 to 2020-12

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-bounces@xxxxxxxxxxx <m2e-users-bounces@xxxxxxxxxxx> On
> Behalf Of KARR, DAVID
> Sent: Friday, December 18, 2020 9:44 AM
> To: m2e-users@xxxxxxxxxxx
> 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@xxxxxxxxxxx
> To unsubscribe from this list, visit
> -users__;!!BhdT!3QmrRTj4Ow0BdJVQU9OXHA1qQVSYJn0ILHzCJw2gEsA72Y7-
> lLvBikdiK1A0Vw$

Back to the top