[
https://issues.apache.org/jira/browse/MNG-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555976#comment-17555976
]
Slawomir Jaranowski commented on MNG-7504:
------------------------------------------
Deprecating will not mitigate warning about unsupported parameter ...
The most download m-site-p by version for May 2022
|| version || % ||
|3.3 | 80,50% |
|3.7.1 | 6,48% |
|3.8.2 | 2,48% |
|3.12.0 | 1,94% |
|3.9.1 | 1,63% |
|3.6 | 1,42% |
|3.5.1 | 1,22% |
of course version binding in Maven is the most popular
So changing version in binding and drop special configuration should not have
big impact.
> Warning about unknown reportPlugins parameters for m-site-p are always
> generated
> --------------------------------------------------------------------------------
>
> Key: MNG-7504
> URL: https://issues.apache.org/jira/browse/MNG-7504
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.9.0, 4.0.0
> Reporter: Slawomir Jaranowski
> Priority: Major
>
> In {{m-site-p 3.7}} configuration parameter {{reportPlugins}} was removed
> MSITE-792
> After MNG-7468 unknown parameter is detected and warning is generated.
> We have service {{org.apache.maven.model.plugin.DefaultReportingConverter}}
> which always add configuration for m-site-p with unsupported parameter
> {{reportPlugins}}.
> Configuration is added when project contains reporting sections.
> Possible solution
> - drop service - easy to implement but with impact on m-site-p < 3.7
> - detect m-site-p version in project - complicated
> - don't print warning about {{reportPlugins}} for {{m-site-p}} - easy but
> workaround
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
