Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.0
Description
M2E has a trick to disable warnings when some plugins are not supported by M2E: by configuring a fake org.eclipse.m2e:lifecycle-mapping plugin in pluginManagement, M2E detects and gets the configuration while nothing is executed during Maven build (see http://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html#ignore-plugin-goal)
But during reporting, this fake/inexistent plugin is downloaded and an annoying failure is shown as error:
[INFO] Generating "Plugin Management" report --- maven-project-info-reports-plugin:3.0.0:plugin-management [INFO] Could not build project for: lifecycle-mapping:Error resolving project artifact: Failure to find org.eclipse.m2e:lifecycle-mapping:pom:1.0.0 in https://repo.maven.apache.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced for project org.eclipse.m2e:lifecycle-mapping:pom:1.0.0
with 3 level of nested stacktrace (not shown here for brevity)
it would be useful to be able to exclude this fake plugin from the MPIR report, then avoid this nasty error