[
https://issues.apache.org/jira/browse/DOXIA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806931#comment-17806931
]
Konrad Windszus edited comment on DOXIA-725 at 1/15/24 6:14 PM:
----------------------------------------------------------------
It makes sense to be able to release Doxia Sitetools alone (without Doxia), but
is no that useful the other way around. To be able to have this flexibility it
is reasonable to have them in dedicated repositories. Also it is a matter of
effort, usually the Doxia changes are done first. Is there any reason why you
cannot stick to Doxia M8 for the moment?
was (Author: kwin):
It makes sense to be able to release Doxia Sitetools alone (without Doxia), but
is no that useful the other way around. To be able to have this flexibility it
is reasonable to have them in dedicated repositories. Also it is a matter of
effort, usually the Doxia changes are done first. Is there any reason why
cannot stick to Doxia M8 for the moment?
> 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)
