[jira] [Updated] (MNG-6189) WARN if maven-site-plugin configuration contains reportPlugins element

["Hervé Boutemy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy updated MNG-6189:
-------------------------------
    Description: 
with MNG-4162, a bunch of reporting logic was removed from Maven core.
This was globally successful, but not on one topic: it was expected to remove pom's {{reporting}} section and replace it with a normal {{reportPlugins}} parameter in maven-site-plugin configuration.
We later discovered that with this normal parameter, we missed one crucial feature: report plugins inheritance, which would require a new mechanism MSITE-484
Then we reverted our instructions in maven-site-plugin documentation MSITE-647: the new {{reportPlugins}} parameter is now just an implementation detail, but should not be used by end-users, {{reporting}} section remains the way to configure report plugins MSITE-684

Now adding a warning in Maven core when it detects a {{reportPlugins}} parameter in a maven-site-plugin configuration is easy to do, will help users come back to normal {{reporting}} configuration, and will permit future enhancements (we need to finally completely clean-up the situation we created with this story...)

  was:
with MNG-4162, a bunch of reporting logic was removed from Maven core.
This was globally successful, but not on one topic: it was expected to remore pom's {{reporting}} section and replace it with a normal {{reportPlugins}} parameter in maven-site-plugin.
We later discovered that with this normal parameter, we missed one crucial feature: report plugins inheritance, which would require a new mechanism MSITE-484
Then we reverted our instructions in maven-site-plugin documentation MSITE-647: the new {{reportPlugins}} parameter is just an implementation detail, but should not be used by end-users, {{reporting}} section remains the way to configure report plugins MSITE-684

Now adding a warning in Maven core when it detects a {{reportPlugins}} parameter in a maven-site-plugin is easy to do, will help users come back to normal {{reporting}} configuration, and will permit future enhancements (we need to finally completely clean-up the situation we created with this story...)


> WARN if maven-site-plugin configuration contains reportPlugins element
> ----------------------------------------------------------------------
>
>                 Key: MNG-6189
>                 URL: https://issues.apache.org/jira/browse/MNG-6189
>             Project: Maven
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation, Sites & Reporting
>    Affects Versions: 3.5.0-alpha-1
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>             Fix For: 3.5.0-alpha-2
>
>
> with MNG-4162, a bunch of reporting logic was removed from Maven core.
> This was globally successful, but not on one topic: it was expected to remove pom's {{reporting}} section and replace it with a normal {{reportPlugins}} parameter in maven-site-plugin configuration.
> We later discovered that with this normal parameter, we missed one crucial feature: report plugins inheritance, which would require a new mechanism MSITE-484
> Then we reverted our instructions in maven-site-plugin documentation MSITE-647: the new {{reportPlugins}} parameter is now just an implementation detail, but should not be used by end-users, {{reporting}} section remains the way to configure report plugins MSITE-684
> Now adding a warning in Maven core when it detects a {{reportPlugins}} parameter in a maven-site-plugin configuration is easy to do, will help users come back to normal {{reporting}} configuration, and will permit future enhancements (we need to finally completely clean-up the situation we created with this story...)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)