[
https://issues.apache.org/jira/browse/MSITE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899164#comment-17899164
]
Philipp Ottlinger commented on MSITE-1026:
------------------------------------------
>From a user's perspective this is really hard - I update my site-plugin and
>all my reports are broken without notice.
The update is not even a breaking change, but only a minor update (e.g. 3.12.1
to 3.21.0) ..... personally I'd really love to give the user a chance to get of
this mess. Filing multiple issues in various deprecated/not maintained
jiras/Github repos does not seem a good solution to me from a platform
perspective. I was always of the belief that Maven tries to be a platform and
guide the user to stay as current as possible.
[~ggregory] 's solution to remain on the old stack will break with a new ASF
parent or other "updates"; configuring ant-regExp exclusions to generate
missing HTML table elements into the report seems errorprone and not
user-friendly at all.
Please close the ticket as you see fit ..... the users will most probably vote
with their feet :(
> 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
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> 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/] - filed a separate
> issue: https://issues.apache.org/jira/browse/MCHANGES-424
> * (20241117: jdepend-plugin - [broken report
> example|https://ottlinger.github.io/fotorenamer/jdepend-report.html] - filed
> a separate issue at
> (GitHubIssues)[https://github.com/mojohaus/jdepend-maven-plugin/issues/43],
> thanks for the clarification [~michael-o] )
> * dev-activity-report - [broken report
> example|https://ottlinger.github.io/fotorenamer/dev-activity.html]
> * file-activity-report - [broken report
> example|https://ottlinger.github.io/fotorenamer/file-activity.html]
> 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)
