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

Hervé Boutemy commented on MPDF-81:
-----------------------------------

to better work together, I migrated Doxia and Doxia Sitetools to git: see 
http://maven.apache.org/doxia/source-repository.html
you can now easily create GitHub pull requests.
I expect this will permit little focused PRs (easier than patches attached to 
Jira): DOXIA-562 monolithic patch for example requires multiple PRs

notice maven-pdf-plugin is not yet migrated to git: this won't happen before a 
few weeks, because we must split 1 svn repo to more than 40 git repositories, 
with Jenkins associated configuration. See 
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos
 if you're interested in details

on the reflection trickery: I understand that adding a bunch of setter in 
FoAggregateSink is not welcome. Reflection on an object that comes from 
maven-pdf-plugin is not an option either.
What can be done IMHO is to create a FoAggregateContext class in Doxia FO 
module: then FO AggregateSink can use it as wanted, and maven-pdf-plugin can 
populate it also.

We can initialize this FoAggregateContext structure with the footerText 
attribute.
WDYT?




> Override the copyright footer
> -----------------------------
>
>                 Key: MPDF-81
>                 URL: https://issues.apache.org/jira/browse/MPDF-81
>             Project: Maven PDF Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.3
>            Reporter: Alex O'Ree
>             Fix For: 1.4
>
>         Attachments: maven-pdf-plugin2.pdf
>
>
> As of right now, it doesn't look possible to override the content of the 
> footer which is on all non-title page pages. It currently reads (c) year - 
> organization All rights reserved.
> I don't see anywhere in the code where this is defined or in any of the 
> resource files. It is in the generated fo files but it's not obvious where 
> the xslt is.



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

Reply via email to