Open issues for the next release

Return-Path: Delivered-To: apmail-forrest-site-svn-archive@minotaur.apache.org Received: (qmail 75726 invoked from network); 8 Feb 2011 09:57:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Feb 2011 09:57:19 -0000 Received: (qmail 23171 invoked by uid 500); 8 Feb 2011 09:57:19 -0000 Delivered-To: apmail-forrest-site-svn-archive@forrest.apache.org Received: (qmail 23078 invoked by uid 500); 8 Feb 2011 09:57:18 -0000 Mailing-List: contact site-svn-help@forrest.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@forrest.apache.org Delivered-To: mailing list site-svn@forrest.apache.org Received: (qmail 22995 invoked by uid 99); 8 Feb 2011 09:57:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 09:57:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 09:57:07 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 2CC342388C27; Tue, 8 Feb 2011 09:56:21 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1068308 [11/12] - in /forrest/site: ./ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ docs_0_80/howto/multi/ docs_0_90/ docs_0_90/howto/ docs_0_90/howto/cvs-ssh/ docs_0_90/howto/multi/ dtdx/ plan/ pluginDocs/ pluginDocs/plugins_0_80/... Date: Tue, 08 Feb 2011 09:56:18 -0000 To: site-svn@forrest.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20110208095621.2CC342388C27@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: forrest/site/forrest-issues.html URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?rev=1068308&r1=1068307&r2=1068308&view=diff ============================================================================== --- forrest/site/forrest-issues.html (original) +++ forrest/site/forrest-issues.html Tue Feb 8 09:56:12 2011 @@ -3,7 +3,7 @@ - + Open issues for the next release @@ -201,16 +201,79 @@ document.write("Last Published: " + docu

+[FOR-911] decide content of release +
+[FOR-812] Remove dependency of projectInfo on skinconf.xml +
+[FOR-1108] Dispatcher, Cocoon 2.1 and Windows +
[FOR-855] verify the license situation prior to each release
-[FOR-1077] new CreationDate causes constant differences in output pdf documents +[FOR-572] run a memory profiler while forrest is operating +
+[FOR-588] Design new configuration system +
+[FOR-986] Dispatcher war fails to build if no skinconf.xml is in place +
+[FOR-970] Add a way to have plugin specific resources, such as its own CSS styling, independent of skin or theme +
+[FOR-1092] review our sitemaps *.xmap to compare with Cocoon-2.1 +
+[FOR-560] Remove duplicate jars from eclipse plugins +
+[FOR-217] Certain patterns are claimed by the default sitemaps +
+[FOR-705] Target of LocationMap rewriteDemo causes build failure when target not available +
+[FOR-1122] Example site contentIntegration currently only works in forrest run mode
-[FOR-1208] NPE exception when generating PDF that includes SVG to PNG image conversion +[FOR-1152] regularly ensure cross-browser consistency
-[FOR-915] changes with PNGs generated on different platforms +[FOR-971] The tables used to output Glossary information needs styling with CSS +
+[FOR-250] only add the compliance logos if the html is valid +
+[FOR-1151] regularly ensure valid CSS +
+[FOR-1202] Easier testing in 'run' mode +
+[FOR-1149] regularly review our example sites +
+[FOR-211] whole-site html and pdf: broken ext links +
+[FOR-889] Use by Ant of newer catalog entity resolver failing for Windows +
+[FOR-1073] link elements with no href are created by html-to-document.xsl for a/name +
+[FOR-1066] Dispatcher started failing on seed sample site recently with out-of-memory error +
+[FOR-1184] using unreleased code for some supporting products +
+[FOR-1150] regularly ensure valid HTML

@@ -226,91 +289,321 @@ document.write("Last Published: " + docu open issues). The listing below is regenerated on each Forrest run. + +

[FOR-911] decide content of release

+https://issues.apache.org/jira/browse/FOR-911 +

For past releases we have essentially done a "source" release, i.e. pack everything found in svn trunk including a pre-built forrest binary jar file. + + + +Here is one recent discussion: + + content of release [was: Re: review list of scheduled issues for 0.8 release] + + <a href="http://marc.theaimsgroup.com/?t=115257903800001">http://marc.theaimsgroup.com/?t=115257903800001</a>

+ +

[FOR-812] Remove dependency of projectInfo on skinconf.xml

+https://issues.apache.org/jira/browse/FOR-812 +

The dispatcher will remove the file skinconf.xml. However, the projectInfo plugin uses it to get the URL for the issue tracker. + + + +We should chage the projectInfo plugin so that this value is provided by a plugin property.

+ +

[FOR-1108] Dispatcher, Cocoon 2.1 and Windows

+https://issues.apache.org/jira/browse/FOR-1108 +

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

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

-https://issues.apache.org:443/jira/browse/FOR-855 +https://issues.apache.org/jira/browse/FOR-855

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 "Fix for Version" on to the next release. + + + +Here are some of the tasks: + + + +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). -Here are some of the tasks: + -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). +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 -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 + C) Remove any author tags.

- -

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

+ +

[FOR-572] run a memory profiler while forrest is operating

+https://issues.apache.org/jira/browse/FOR-572 +

We need to run a memory profiler while forrest is operating.

+ +

[FOR-588] Design new configuration system

+https://issues.apache.org/jira/browse/FOR-588 +

We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins.

+ +

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

-https://issues.apache.org:443/jira/browse/FOR-1077 +https://issues.apache.org/jira/browse/FOR-986

A problem has recently occurred with generating PDFs and publishing them. See the massive amount of commits to the Forrest "site" 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. +

A dispatcher based site does not need a skinconf.xml file. However, if one is not present then the "forrest war" target fails with: + + + +BUILD FAILED + +C:\projects\apache-forrest-0.8\main\targets\webapp.xml:48: The following error occurred while executing this line: + +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 + + + +To work around this issue just put a skinconf.xml in place

+ +

[FOR-970] Add a way to have plugin specific resources, such as its own CSS styling, independent of skin or theme

+https://issues.apache.org/jira/browse/FOR-970 +

It would be nice if plugins could be a little more independent of core skins and themes for plugin specific styling. + +This could be CSS, or something else, I have only identified CSS needs at present.

+ +

[FOR-1092] review our sitemaps *.xmap to compare with Cocoon-2.1

+https://issues.apache.org/jira/browse/FOR-1092 +

Compare our main sitemap files with Cocoon-2.1 where some properties are configurable via WEB-INF/properties/ files.

+ +

[FOR-560] Remove duplicate jars from eclipse plugins

+https://issues.apache.org/jira/browse/FOR-560 +

tools/eclipse/plugins/org.apache.forrest.eclipse.servletEngine/lib contains some duplicate jars to those in the main Forrest trunk. We should find a way of reusing the jars from their existing location.

+ +

[FOR-217] Certain patterns are claimed by the default sitemaps

+https://issues.apache.org/jira/browse/FOR-217 +

Users are prevented from using certain filenames because those patterns are claimed by the default sitemaps for special processing. These include: site, changes, todo, faq, images, my-images, skinconf, cprofile

- -

[FOR-1208] NPE exception when generating PDF that includes SVG to PNG image conversion

+ +

[FOR-705] Target of LocationMap rewriteDemo causes build failure when target not available

-https://issues.apache.org:443/jira/browse/FOR-1208 +https://issues.apache.org/jira/browse/FOR-705

The "seed-sample" site has two examples of converting to PNG from SVG at linking.html#images +

Build fails when given target URL of rewriteDemo is not available (site down, no longer exists, incorrect URL typing etc). -This works okay with HTML output. It is also okay with PDF output. The images are generated. +For various reasons given in [1] and [2] this default feature should remain but alternative options should be made available. Possible solutions given in [3] -However with the PDF, there is also a NullPointerException +[1] <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112826350500282">http://marc.theaimsgroup.com/?l=forrest-dev&m=112826350500282</a> -To stop it, comment-out the two examples for "ellipse".

+[2] <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=11270994920771">http://marc.theaimsgroup.com/?l=forrest-dev&m=11270994920771</a> + + + +[3] <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112859428219336&w=2">http://marc.theaimsgroup.com/?l=forrest-dev&m=112859428219336&w=2</a> + + + +

- -

[FOR-915] changes with PNGs generated on different platforms

+ +

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

-https://issues.apache.org:443/jira/browse/FOR-915 +https://issues.apache.org/jira/browse/FOR-1122

<a href="http://marc.theaimsgroup.com/?t=115450117900002&r=1&w=2">http://marc.theaimsgroup.com/?t=115450117900002&r=1&w=2</a> +

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

+ +

[FOR-1152] regularly ensure cross-browser consistency

+https://issues.apache.org/jira/browse/FOR-1152 +

Review the sites using cross-browser testing tools.

+ +

[FOR-971] The tables used to output Glossary information needs styling with CSS

+https://issues.apache.org/jira/browse/FOR-971 +

I would like to align the table columns with percentage CSS like 20-60-20 to improve the look and readability.

+ +

[FOR-250] only add the compliance logos if the html is valid

+https://issues.apache.org/jira/browse/FOR-250 +

Currently the compliance logos are only applied to any page called "index.html". It would be nice if we could automatically determine if the final output was valid and apply the compliance logos accordingly.

+ +

[FOR-1151] regularly ensure valid CSS

+https://issues.apache.org/jira/browse/FOR-1151 +

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-1202] Easier testing in 'run' mode

+https://issues.apache.org/jira/browse/FOR-1202 +

We need an automated way to test forrest in run mode. I think a nice simple start would be to simply do an http request and assert HTTP.StatusCode == 200. I think this doesn't need to be hard a couple options: -> > Modified: + -> > forrest/site/committed-1.png +1) Use HttpClient to retrieve abs-menulinks and attempt to visit anyone with some configured domain (e.g. localhost). -> > forrest/site/live-sites.html + -> > forrest/site/live-sites.pdf +2) Use a crawler to do something similar. -> > forrest/site/skin/images/rc-b-l-15-1body-2menu-3menu.png + -> > forrest/site/skin/images/rc-b-r-15-1body-2menu-3menu.png +3) ? -> > forrest/site/skin/images/rc-b-r-5-1header-2tab-selected-3tab-selected.png + -> > forrest/site/skin/images/rc-t-l-5-1header-2searchbox-3searchbox.png +it could get more sophisticated later, a simple 200(Ok) is a good start I think. -> > forrest/site/skin/images/rc-t-l-5-1header-2tab-selected-3tab-selected.png +--tim

+ +

[FOR-1149] regularly review our example sites

+https://issues.apache.org/jira/browse/FOR-1149 +

We need to continually re-assess our example sites, to ensure such things as xml validation, css validation, and cross-browser consistency. + + + +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-211] whole-site html and pdf: broken ext links

+https://issues.apache.org/jira/browse/FOR-211 +

In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).

+ +

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

+https://issues.apache.org/jira/browse/FOR-889 +

Some people on Windows report that the 'forrest validate-xdocs' task is "failing" when we upgrade the $FORREST_HOME/tools/ant/lib/xml-commons-resolver.jar -> > forrest/site/skin/images/rc-t-l-5-1header-2tab-unselected-3tab-unselected.png + -> > forrest/site/skin/images/rc-t-r-15-1body-2menu-3menu.png +See discussion in: -> > forrest/site/skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png + [heads up] Ant upgraded, please test -> > forrest/site/skin/images/rc-t-r-5-1header-2tab-selected-3tab-selected.png + <a href="http://marc.theaimsgroup.com/?t=114800390100001">http://marc.theaimsgroup.com/?t=114800390100001</a>

+ +

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

+https://issues.apache.org/jira/browse/FOR-1073 +

In <a href="https://issues.apache.org/jira/browse/FOR-1072" title="[PATCH] Bugfixes and improvements for PDF output plugin"><strike>FOR-1072</strike></a> Jeremias said: -> > forrest/site/skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png +"Filtered out link elements with no href (which are created by html-to-document.xsl for "<a name=..."). Forrest 0.7 didn't generate them as links at all but trunk does. Maybe that's wrong in the first place. " -We cannot explain why this changes occur.

+There was also a mention of it previously on the dev list surrounding the recent FOP update branch work.

+ +

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

+https://issues.apache.org/jira/browse/FOR-1066 +

cd $FORREST_HOME/main + +./build.sh test + +                                                                                                  &nbsp ;                             + +The first stage (the skins-based site) builds fine. + +The second stage (the dispatcher-based site) hangs. + + + +See email: + +<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> + +Re: dispatcher hanging with out of memory errors

+ +

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

+https://issues.apache.org/jira/browse/FOR-1184 +

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

+ +

[FOR-1150] regularly ensure valid HTML

+https://issues.apache.org/jira/browse/FOR-1150 +

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>

Apache Forrest 0.9 was released on 2011-02-07. Consolidation. +

Apache Forrest 0.8 was released on 2007-04-18. Locationmaps define the mapping from requests to locations, which enables content and resources to be located at various @@ -496,7 +499,7 @@ document.write("Last Published: " + docu Copyright © 2002-2011 The Apache Software Foundation. Licensed under Apache License 2.0
- Apache, Apache Forrest, the Apache feather logo, and the Apache Forrest + Apache Forrest, Forrest, Apache, the Apache feather logo, and the Apache Forrest logos are trademarks of The Apache Software Foundation.

Modified: forrest/site/issues.html URL: http://svn.apache.org/viewvc/forrest/site/issues.html?rev=1068308&r1=1068307&r2=1068308&view=diff ============================================================================== --- forrest/site/issues.html (original) +++ forrest/site/issues.html Tue Feb 8 09:56:12 2011 @@ -3,7 +3,7 @@ - + Apache Forrest issue tracker @@ -491,7 +491,7 @@ document.write("Last Published: " + docu Copyright © 2002-2011 The Apache Software Foundation. Licensed under Apache License 2.0
- Apache, Apache Forrest, the Apache feather logo, and the Apache Forrest + Apache Forrest, Forrest, Apache, the Apache feather logo, and the Apache Forrest logos are trademarks of The Apache Software Foundation.