[jira] [Commented] (DOXIA-725) Latest doxia-coreM9 is not compatible with doxia-sitetools

["Abel Salgado Romero (Jira)" <ji...@apache.org>]

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

Abel Salgado Romero commented on DOXIA-725:
-------------------------------------------

I just noted that since asciidoctor-maven-site 4.0.0-M4 the modules are not even detected. I assume there are some internal big changes.

I found this [https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack#TowardsDoxia2.0.0Stack-ReportingPluginMaintainers,] but there's no migration guide or detail on what do to.

> Latest doxia-coreM9 is not compatible with doxia-sitetools
> ----------------------------------------------------------
>
>                 Key: DOXIA-725
>                 URL: https://issues.apache.org/jira/browse/DOXIA-725
>             Project: Maven Doxia
>          Issue Type: Improvement
>            Reporter: Abel Salgado Romero
>            Priority: Major
>
> Testing Milestones I found `doxia-core` 4.0.0-M9 is not compatible with `doxia-sitetools`.
> This commit [https://github.com/apache/maven-doxia/commit/0dfe227b6603151b8b460d2b7cacc8953a512f4f] final methods where added to `AbstractSink` class, those are still present in sub-classes like `SiteRendererSink` which now fail instantiation with:
> ```
> java.lang.IncompatibleClassChangeError: class org.apache.maven.doxia.siterenderer.sink.SiteRendererSink overrides final method org.apache.maven.doxia.sink.impl.AbstractSink.head(
> ```



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