[
https://issues.apache.org/jira/browse/DOXIA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807218#comment-17807218
]
Michael Osipov edited comment on DOXIA-725 at 1/16/24 12:26 PM:
----------------------------------------------------------------
[~Abel S.Romero], no offense taken. One of the problems with a BOM that most of
them stack,so have to go through all releases and do a BOM with a separate
project of which you need only fraction. I am not completely sure how much
better the BOM would be...This is, though, something we should consider after
all of the changes have been done.
was (Author: michael-o):
[~Abel S.Romero], no offense taken. One of the problems with a BOM that most of
them stack,so have to go through all releases and do a BOM with a separate
project of which you need only fraction. I am not completely sure how much
better the BOM would be...
> 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)
