Hervé Boutemy created MPIR-375:
----------------------------------
Summary: add plugin excludes feature
Key: MPIR-375
URL: https://issues.apache.org/jira/browse/MPIR-375
Project: Maven Project Info Reports Plugin
Issue Type: New Feature
Components: dependency-management
Affects Versions: 3.0.0
Reporter: Hervé Boutemy
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
But during reporting, this fake/inexistent plugin is downloaded and an annoying
failure is shown as error:
{noformat}[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{noformat}
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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
