[
https://issues.apache.org/jira/browse/MPLUGIN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MPLUGIN-386:
------------------------------------
Summary: Filter out maven-archiver and maven-jxr from scope warning (was:
Lower the tone and limit the scope check to maven-plugin-api only)
> Filter out maven-archiver and maven-jxr from scope warning
> ----------------------------------------------------------
>
> Key: MPLUGIN-386
> URL: https://issues.apache.org/jira/browse/MPLUGIN-386
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Plugin
> Affects Versions: 3.6.2
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 3.6.3
>
>
> The warning emitted by m-p-p added as part of MPLUGIN-370 triggers for too
> broad set of artifacts (most notably maven-archiver and maven-jxr, that needs
> to be mentioned, are simply in wrong groupID), and is too chatty.
> As minor bugfix, proposal is to make the warning message be changed as:
> * triggered only if maven-plugin-api is NOT in provided scope
> * emit a one liner message like "It is best practice to keep
> maven-plugin-api dependency in provided scope."
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
