[jira] [Commented] (MSITE-1026) How to go ahead as a user of unsupported plugins - is there a documentation available to fix (newly built) broken site-webpages

["Gary D. Gregory (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSITE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898783#comment-17898783 ] 

Gary D. Gregory commented on MSITE-1026:
----------------------------------------

Hello [~pottlinger] 

My solution is to set the version of plugins (with a comment) in commons-parent.

Maybe one day someone will care and fork the plugin. Until then, no plugin bumps.

> How to go ahead as a user of unsupported plugins - is there a documentation available to fix (newly built) broken site-webpages
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-1026
>                 URL: https://issues.apache.org/jira/browse/MSITE-1026
>             Project: Maven Site Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.21.0
>            Reporter: Philipp Ottlinger
>            Priority: Critical
>
> If I understood correctly some of the plugins are not planned for migration to the new doxia stack, such as:
> * maven-changes-plugin - https://maven.apache.org/plugins/maven-changes-plugin/
> From a consumer perspective that results in broken site reports as the new layout does not play well with the new maven-site-plugin as can be seen by comparing OLD (pre-2.x) and NEW (doxia-2.x) on Apache Creadur:
> * OLD - formatted ok:
> ** https://creadur.apache.org/rat/
> ** https://creadur.apache.org/rat/changes-report.html
> ** https://creadur.apache.org/rat/jira-report.html 
> * NEW - broken layout: test deployed while working on RAT-397
> ** https://creadur.apache.org/RAT-397/
> ** https://creadur.apache.org/RAT-397/changes-report.html
> ** https://creadur.apache.org/RAT-397/jira-report.html
> Via chat [~michaelo] suggested that there is a way to configure a post-site step that transforms the old format into the new format .... where can I find more details or examples on what to do in order to accomplish a more complete and correctly formatted site/webpage with the new stack.
> Thanks for any help, hints, examples or documentation
> -------
> [~ggregory] does commons have a solution for the problem? How do you solve the problem?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)