hboutemy edited a comment on pull request #31: URL: https://github.com/apache/maven-apache-parent/pull/31#issuecomment-755940000
@michael-o I proposed PR #34 for the way I see MPOM-260 to be solved: review welcome before I merge to master @kwin thanks for the pointers to many locations in the site that should be updated/enhanced: I did much work on this in the past, but I missed some FYI, I finally remembered where I wrote the reference documentation of how reporting management evolves over time: it's in reporting-exec, given it's where the direct evolution was coded https://maven.apache.org/shared/maven-reporting-exec/ This component documentation is really **the** reference documentation for that aspect, because that's where code is, then is documented when it evolves. The [history page on maven-site-plugin](https://maven.apache.org/plugins/maven-site-plugin/history.html) was an addition I did later to have a chance to see from a user point of view, who knows only about maven-site-plugin version, what is in each version (be it from evolution coded in Doxia, Doxia Site Tools or Maven Reporting Executor) And I did not fight against removing maven-3.html page from 3.9.1 in #20 , because I knew this page was too complex (and I can't fight against every time people try to do cleanup, even if I'm convinced that I'll be hit like here...), but this is where in the past evolution was described in detail: https://maven.apache.org/plugins-archives/maven-site-plugin-3.9.0/maven-3.html I moved MNG-7006 to https://issues.apache.org/jira/browse/MNGSITE-440 because that's a better Jira project: let's track in this Jira issue the documentation improvement ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org