[
https://issues.apache.org/jira/browse/DOXIA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806979#comment-17806979
]
Abel Salgado Romero commented on DOXIA-725:
-------------------------------------------
I don't mean to criticize the amazing work, but it's hard to consume those
components. The relationship is non-obvious; for instance, you cannot use
automatic bumping, and as shown, when you see incompatibilities the code does
not reflect you should be using the same version
[https://github.com/apache/maven-doxia-sitetools/blob/5fe4a4c5359e6a23b78f385e15f77767cadaee99/pom.xml#L32-L70.]
Maybe a BOM could be published that takes care of the dependencies?
> Latest Doxia Core is not compatible with doxia-sitetools
> --------------------------------------------------------
>
> Key: DOXIA-725
> URL: https://issues.apache.org/jira/browse/DOXIA-725
> Project: Maven Doxia
> Issue Type: Improvement
> Affects Versions: 2.0.0-M9
> Reporter: Abel Salgado Romero
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> 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)
