apache > forrest
Font size:      

Open issues for the next release

These are the top 25 open issues for the next release that are scheduled in our issue tracking system (see all open issues). The listing below is regenerated on each Forrest run.

[FOR-796] Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core


This is the global issue to keep track on the merging effort

[FOR-868] add relevant notes to the "Upgrading" xdoc


We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to <a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"><strike>FOR-865</strike></a> &quot;Add missing entries to status.xml to generate the changes list&quot;.

[FOR-855] verify the license situation prior to each release


This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the &quot;Fix for Version&quot; on to the next release.<br/> <br/> Here are some of the tasks:<br/> <br/> A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).<br/> <br/> B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt<br/> <br/> C) Remove any author tags.

[FOR-1108] Dispatcher, Cocoon 2.1 and Windows


Since the update to Cocoon 2.1 Forrest and Dispatcher have broken on windows.

[FOR-986] Dispatcher war fails to build if no skinconf.xml is in place


A dispatcher based site does not need a skinconf.xml file. However, if one is not present then the &quot;forrest war&quot; target fails with:<br/> <br/> BUILD FAILED<br/> C:\projects\apache-forrest-0.8\main\targets\webapp.xml:48: The following error occurred while executing this line:<br/> C:\projects\apache-forrest-0.8\main\forrest.build.xml:256: input file C:\projects\apache-forrest-0.8\main\webapp\skinconf.xml does not exist<br/> <br/> To work around this issue just put a skinconf.xml in place

[FOR-922] update all docs that explain sitemap fragments


There are various documents that explain parts of the sitemaps. Some of these mention pathnames, some have actual fragments of code copied from sitemaps. All of this needs to be updated to reflect the current sitemaps. <br/> <br/> The sitemaps were recently updated to use locationmap, some sitemaps were simplified, filenames were changed, e.g. document2html.xsl to document-to-html.xsl <br/> <br/> These changes need to be reflected in the current docs.

[FOR-857] append license files to the top-level LICENSE.txt


The license files for accompanying external products needs to be appended after the Apache License in the top-level $FORREST_HOME/LICENSE.txt file. <br/> <br/> Perhaps the current discussion on the legal-discuss mailing list will clarify <br/> <a href="http://www.apache.org/foundation/mailinglists.html#foundation-legal">http://www.apache.org/foundation/mailinglists.html#foundation-legal</a>

[FOR-1066] Dispatcher started failing on seed sample site recently with out-of-memory error


cd $FORREST_HOME/main <br/> ./build.sh test <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/> The first stage (the skins-based site) builds fine. <br/> The second stage (the dispatcher-based site) hangs.<br/> <br/> See email:<br/> <a href="http://mail-archives.apache.org/mod_mbox/forrest-dev/200801.mbox/%3c20080131070310.GE2051@igg.indexgeo.com.au%3e">http://mail-archives.apache.org/mod_mbox/forrest-dev/200801.mbox/%3c20080131070310.GE2051@igg.indexgeo.com.au%3e</a><br/> Re: dispatcher hanging with out of memory errors

[FOR-1077] new CreationDate causes constant differences in output pdf documents


A problem has recently occurred with generating PDFs and publishing them. See the massive amount of commits to the Forrest &quot;site&quot; svn today when two different committers updated the website. Every PDF changed. I did some investigation and can see that a CreationDate is being added. This is of course is changing on every run of forrest.<br/> <br/>

[FOR-1184] using unreleased code for some supporting products


After the last release, an issue was brought to our attention about using unreleased code from other projects.

[FOR-889] Use by Ant of newer catalog entity resolver failing for Windows


Some people on Windows report that the 'forrest validate-xdocs' task is &quot;failing&quot; when we upgrade the $FORREST_HOME/tools/ant/lib/xml-commons-resolver.jar<br/> <br/> See discussion in:<br/> &nbsp;[heads up] Ant upgraded, please test<br/> &nbsp;<a href="http://marc.theaimsgroup.com/?t=114800390100001">http://marc.theaimsgroup.com/?t=114800390100001</a>

[FOR-1122] Example site contentIntegration currently only works in forrest run mode


Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations.

[FOR-1104] pdf output warnings "paragraph overflows the available area"


Warnings are issued such as the following from our &quot;site-author&quot;:<br/> <br/> WARN - Line 1 of a paragraph overflows the available area. (fo:block, &quot;project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.o)<br/> <br/> These come from &quot;source&quot; elements with content that has lines that are too wide, e.g.<br/> pluginDocs/plugins_0_90/usingPlugins.xml<br/> <br/> Perhaps there some way that we can word-wrap or break the long text lines.

[FOR-1103] Move output.inputModule code into core


As discussed and decided in the thread<br/> <br/> <a href="http://www.mail-archive.com/dev@forrest.apache.org/msg14705.html">http://www.mail-archive.com/dev@forrest.apache.org/msg14705.html</a><br/> <br/> see esp. the message:<br/> <br/> <a href="http://marc.info/?l=forrest-dev&m=122030056505478&w=2">http://marc.info/?l=forrest-dev&amp;m=122030056505478&amp;w=2</a><br/> <br/> we want to move the code for the output.inputModule into the core, to get rid of plugin dependencies. This should be done before we release 0.9.<br/> <br/> This issue is created just to not loose track of it.

[FOR-1152] regularly ensure cross-browser consistency


Review the sites using cross-browser testing tools.

[FOR-1149] regularly review our example sites


We need to continually re-assess our example sites, to ensure such things as xml validation, css validation, and cross-browser consistency.<br/> <br/> Please leave this issue and subtasks as an open reminder of what needs to be done. Create separate issues for each problem that arises.

[FOR-1150] regularly ensure valid HTML


Ensure that HTML validates okay for the test document referred to in the parent issue. Use <a href="http://validator.w3.org/">http://validator.w3.org/</a>

[FOR-1151] regularly ensure valid CSS


Ensure that CSS validates okay for the test document referred to in the parent issue. Use <a href="http://jigsaw.w3.org/css-validator/">http://jigsaw.w3.org/css-validator/</a>

[FOR-1165] Samples Tab does not stay highlighted when sub-tab or sub-tab menu items are chosen - Pelt Theme


Choose the 'Samples' tab and it correctly highlights. <br/> Then choose either 'Samples1' or 'Samples2' sub-tab and the 'Samples' highlight is removed. Correct behaviour as per Pelt Skin is for the highlighting color to remain.

[FOR-644] code-style cleanup for xml files


We have much inconsistent whitespace in all of our files. This is known to cause trouble in a collaborative environment. See discussion at: <a href="http://marc.theaimsgroup.com/?t=112450901100001">http://marc.theaimsgroup.com/?t=112450901100001</a> and <a href="http://marc.theaimsgroup.com/?t=112495618800002">http://marc.theaimsgroup.com/?t=112495618800002</a> and various linked discussions.<br/>

[FOR-1073] link elements with no href are created by html-to-document.xsl for a/name


In <a href="http://issues.apache.org/jira/browse/FOR-1072" title="[PATCH] Bugfixes and improvements for PDF output plugin"><strike>FOR-1072</strike></a> Jeremias said:<br/> &quot;Filtered out link elements with no href (which are created by html-to-document.xsl for &quot;&lt;a name=...&quot;). Forrest 0.7 didn't generate them as links at all but trunk does. Maybe that's wrong in the first place. &quot;<br/> <br/> There was also a mention of it previously on the dev list surrounding the recent FOP update branch work.

[FOR-1187] upgraded PDF plugin was not deployed properly


Around January 2008 the PDF plugin was upgraded, gaining functionality that was only relevant to forrest-0.9-dev. It was re-deployed without changing the version numbers in the plugin descriptor.

[FOR-1166] Search Button is misplaced to the right in some browsers - Pelt Theme


The 'Search' Button used with the 'Search the site with ...' Feature is not correctly situated in Firefox on Linux machines. It is way off to the right, making the site pages horizontally scroll apart from it being ugly. <br/> <br/> Interestingly, it looks fine in Firefox on Windows. Also looks good in IE7 and Google Chrome on Windows.

[FOR-1069] add notices for US cryptographic export laws


We need to investigate our SVN and add crypto notices as explained at <a href="http://www.apache.org/licenses/exports/">http://www.apache.org/licenses/exports/</a> and the legal-discuss mail list.

[FOR-1168] Sample pages that fail validation


The main 'sample.html' passes validation fine, however some other pages fail xhtml 1.0 strict validation. Mainly due to the use of the + symbol in name anchors. Not a problem for sites validating to HTML4.01. <br/> <br/> These pages include (but check for more) <br/> <br/> samples-b/usemap.html <br/> samples-b/xinclude.html <br/> samples-b/static.html <br/> samples-b/linking.html <br/> samples-b/howto-wowto.html <br/> samples-b/embedded_html.html <br/> samples-b/ascii-art.html <br/> locationmap/index.html <br/> samples-c/subdir/index.html <br/> samples-c/showonlywhenselected/page1.html <br/> samples-c/showonlywhenselected/page2.html <br/> pluginDocs/plugins_0_90/index.html <br/> <br/>