maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MPIR-375) add plugin excludes feature for plugin-management report
Date Sun, 25 Nov 2018 19:41:00 GMT


ASF GitHub Bot commented on MPIR-375:

belingueres opened a new pull request #7: [MPIR-375] add plugin excludes feature for plugin-management
   Added pluginManagementExcludes list parameter.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> add plugin excludes feature for plugin-management report
> --------------------------------------------------------
>                 Key: MPIR-375
>                 URL:
>             Project: Maven Project Info Reports Plugin
>          Issue Type: New Feature
>          Components: plugin-management
>    Affects Versions: 3.0.0
>            Reporter: Hervé Boutemy
>            Priority: Major
>              Labels: up-for-grabs
> 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
> 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
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

View raw message