[
https://issues.apache.org/jira/browse/DOXIA-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452219#comment-17452219
]
Herve Boutemy commented on DOXIA-623:
-------------------------------------
yes, as expected, there is a chain of dependencies, then of impact: Doxia's
DOXIA-623 implies Doxia Sitetools DOXIASITETOOLS-236 that implies an equivalent
to MPDF...
AFAIK, maven-pdf-plugin is the only use of document rendering done with Doxia,
in PDF (I don't even know any use for RTF): perhaps we could ask the community
if there is other unexpected impact
And on deprecating or not, the key question is making maintenance effective:
the reality is that current PDF or RTF rendering code is mainly untested when
doing Doxia + Doxia Sitetools releases, because the key (only?) use case is
maven-site-plugin
But thinking at it twice, perhaps one thing we can do is move Doxia and Doxia
Sitetools PDF rendering modules to maven-pdf-plugin: at least, this would make
clear that the Maven plugin is the result of other Doxia* modules, and I'm sure
it would even make their maintenance easier (because I remember having tried to
maintain maven-pdf-plugin in the past, and the need to Doxia* releases was a
pain)
Just an idea, to let community make better decisions on what to do and how to
contribute if they want that the plan is improved to more ambitious than
deprecate...
> Deprecate doxia-module-fo
> -------------------------
>
> Key: DOXIA-623
> URL: https://issues.apache.org/jira/browse/DOXIA-623
> Project: Maven Doxia
> Issue Type: Task
> Components: Module - FO
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 1.11, 1.11.1
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
