crossley at apache
Jan 13, 2011, 5:18 PM
Post #1 of 1
svn commit: r1058828 - /forrest/trunk/site-author/content/xdocs/docs_0_90/upgrading_09.xml
Date: Fri Jan 14 01:18:42 2011
New Revision: 1058828
Add a "upgrade" note about the new PDF plugin.
--- forrest/trunk/site-author/content/xdocs/docs_0_90/upgrading_09.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/upgrading_09.xml Fri Jan 14 01:18:42 2011
@@ -163,6 +163,35 @@
(added in v0.9 - <a href="site:faq/sitemap-entities">FAQ</a>).
+ <section id="pdf">
+ <title>Improved PDF output plugin</title>
+ Many plugins have been upgraded and there are some new plugins.
+ See the <a href="site:changes">Changes</a> and the <a href="site:pluginVersions/overview">Plugins</a>
+ In particular, the PDF output plugin has many improvements, uses a newer Apache FOP etc.
+ It is much more configurable, See its plugin documentation.
+ However there is a minor, but annoying, problem.
+ See <a href="https://issues.apache.org/jira/browse/FOR-1077">FOR-1077</a>.
+ Forrest (via Cocoon) re-generates every document. Every PDF now gets differences
+ due to some internal metadata dates, even though its content might not have changed.
+ When the documentation set is deployed, e.g. via svn, these changed files will also
+ be deployed.
+ For the Forrest project website, we decided to stop (via skinconf.xml) using PDFs
+ for every page and do it only for some specific documents.
+ Remember that if you need to use an old version of any plugin, then it can be
+ specified in forrest.properties by appending the version number (e.g. "-0.2" or "-0.3")
+ to the required plugin name.
<title>Notes about documentation</title>
@@ -172,8 +201,8 @@
there are example snippets of sitemaps which have not yet been upgraded
to reflect the changes to the sitemaps and the separation of some core
stuff into plugins. See issues
- <a href="http://issues.apache.org/jira/browse/FOR-546">FOR-546</a> and
- <a href="http://issues.apache.org/jira/browse/FOR-922">FOR-922</a> and
+ <a href="https://issues.apache.org/jira/browse/FOR-546">FOR-546</a> and
+ <a href="https://issues.apache.org/jira/browse/FOR-922">FOR-922</a> and