NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'

[hboutemy]

Affected version

3.7.0,3.8.0,3.9.0

Bug description

Stacktrace in build output hides a run failure that cuts the report: for example dependency-info is cut after Maven coordinates in 3.7.0 instead of normal list of coordinates before

Here are the strack trace that affects 5 reports from MPIR:
1.

[INFO] Generating "Maven Coordinates" report --- maven-project-info-reports-plugin:3.8.0:dependency-info
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:dependency-info report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
    at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText (AbstractMavenReportRenderer.java:346)
    at org.apache.maven.report.projectinfo.DependencyInformationReport$DependencyInformationRenderer.renderDependencyInfo (DependencyInformationReport.java:217)
    at org.apache.maven.report.projectinfo.DependencyInformationReport$DependencyInformationRenderer.renderMavenPluginCoordinates (DependencyInformationReport.java:156)
    at org.apache.maven.report.projectinfo.DependencyInformationReport$DependencyInformationRenderer.renderBody (DependencyInformationReport.java:135)
    at org.apache.maven.reporting.AbstractMavenReportRenderer.render (AbstractMavenReportRenderer.java:76)
    at org.apache.maven.report.projectinfo.DependencyInformationReport.executeReport (DependencyInformationReport.java:87)
    at org.apache.maven.reporting.AbstractMavenReport.generate (AbstractMavenReport.java:358)

[INFO] Generating "CI Management" report --- maven-project-info-reports-plugin:3.8.0:ci-management
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:ci-management report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
    at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimLink (AbstractMavenReportRenderer.java:367)

[INFO] Generating "Issue Management" report --- maven-project-info-reports-plugin:3.8.0:issue-management
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:issue-management report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
    at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimLink (AbstractMavenReportRenderer.java:367)

[INFO] Generating "Licenses" report      --- maven-project-info-reports-plugin:3.8.0:licenses
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:licenses report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
    at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText (AbstractMavenReportRenderer.java:346)

[INFO] Generating "Source Code Management" report --- maven-project-info-reports-plugin:3.8.0:scm
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:scm report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
    at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimLink (AbstractMavenReportRenderer.java:367)

[hboutemy]

seems related to switch to Maven Reporting 4 / Doxia 2 https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-3.7.0/dependencies.html
when previously was using Maven Reporting 3 / Doxia 1 https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-3.6.2/dependencies.html
done in https://issues.apache.org/jira/browse/MPIR-454

[hboutemy]

given Doxia is provided by maven-site-plugin https://maven.apache.org/plugins/maven-site-plugin/history.html#maven-site-plugin-vs-doxia-vs-doxia-sitetools

I see we have 2 options:

1. use maven-site-plugin 3.21.0, that provides Doxia 2: it would be useful to document that prerequisite in MPIR if this is really a hard upgrade we want to force
2. improve Maven Reporting Impl to be able to emulate Doxia 2 API with Doxia 1, then keep a plugin that is compatible with Doxia 1 and 2, then compatible with maven-site-plugin 3.x and 3.20+

having report plugins compatible with any maven-site-plugin version is my preferred option

[hboutemy]

maven-reporting-impl's https://issues.apache.org/jira/browse/MSHARED-1364 looks in the same spirit: make sure maven-reporting-impl works both with Doxia 1 and 2 (IIUC)

[slawekjaranowski]

1. use maven-site-plugin 3.21.0, that provides Doxia 2: it would be useful to document that prerequisite in MPIR if this is really a hard upgrade we want to force

we can add notice to release notes - eg like in https://github.com/mojohaus/taglist-maven-plugin/releases