maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (DOXIA-555) Footer overrides for FO/PDF outputs
Date Sat, 09 Sep 2017 16:37:02 GMT

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

Hervé Boutemy commented on DOXIA-555:
-------------------------------------

regarding SNAPSHOTs, we don't have choice: we must use them to make change that are transverse
to multiple components (here Doxia and Doxia Sitetools)

then regarding the cycle, which is the key issue: I did a schema to describe how Doxia Sitetools
uses Doxia http://maven.apache.org/doxia/doxia-sitetools/index.html

IMHO, Doxia Sitetools should not inject a generic context to Doxia as Object, with Doxia getting
content with reflection, knowing that the Object is from Doxia SItetool.
Instead Doxia should provide setters for useful properties as Strings, and Doxia Sitetool
should call these setters: perhaps a configuration object would be useful, like DocumentProperties
(which seems useful in case of FO or iText, which are inherently page/document oriented)

> Footer overrides for FO/PDF outputs
> -----------------------------------
>
>                 Key: DOXIA-555
>                 URL: https://issues.apache.org/jira/browse/DOXIA-555
>             Project: Maven Doxia
>          Issue Type: New Feature
>          Components: Module - FO
>            Reporter: Alex O'Ree
>         Attachments: DOXIA-555.patch
>
>
> Related https://issues.apache.org/jira/browse/MPDF-81
> I have a use case where I cannot have the copyright symbol on the bottom of generated
PDF documents. Currently, it looks like the footer is hard coded and cannot be customized.
> http://svn.apache.org/viewvc/maven/doxia/doxia/tags/doxia-1.7/doxia-modules/doxia-module-fo/src/main/java/org/apache/maven/doxia/module/fo/FoAggregateSink.java?view=markup#l762
> ideally, this should be configurable either properties or better yet, the pdf descriptor
document (maven-pdf-plugin). This would require a change in the schema used for the pdf descriptor
http://maven.apache.org/xsd/document-1.0.1.xsd 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message