[
https://issues.apache.org/jira/browse/MCHANGES-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899023#comment-17899023
]
Philipp Ottlinger commented on MCHANGES-424:
--------------------------------------------
I was not sure if MCHANGES-423 meant the same thing as it was only filed with a
low criticality.
To me this seems a blocker as I'm unable to use recommended versions of
Maven-Site-Plugin as long as the changes plugin is not working anymore.
The mentioned workaround is not documented somewhere, which is why I initially
filed the issue as MSITE-1026 to indicate that the migration cannot be
performed easily from a customer perspective.
> Broken layout with doxia-2.x site configurations
> ------------------------------------------------
>
> Key: MCHANGES-424
> URL: https://issues.apache.org/jira/browse/MCHANGES-424
> Project: Maven Changes Plugin
> Issue Type: Bug
> Reporter: Philipp Ottlinger
> Priority: Critical
>
> After migrating to doxia-2.x most of the reports of maven-changes-plugin have
> broken layouts.
>
> The suggestion was to manually fix the HTML in a post-site phase, but I
> wonder if there is a solution available from within MavenChangesPlugin. Is
> there a way to use the maven-changes-plugin with the new stack?
>
> Having to stay with the old/deprecated stack is not an option.
>
> Not sure if MCHANGES-423 means the same problem, but MSITE-1026 contains some
> more information and examples of broken reports.
>
> Thanks for any hints & help on how to proceed with the doxia-2.x migration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
