Modified: forrest/site/forrest-issues.html URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=375162&r1=375161&r2=375162&view=diff ============================================================================== --- forrest/site/forrest-issues.html (original) +++ forrest/site/forrest-issues.html Sun Feb 5 18:30:44 2006 @@ -1,7 +1,7 @@ - + @@ -184,13 +184,13 @@
@@ -268,7 +268,27 @@ all open issues). The listing below is regenerated on each Forrest run.
- + +

[FOR-591] MaxMemory needs increasing

+
+

+http://issues.apache.org/jira/browse/FOR-591 +

+

Since the docs restructurng for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site. +<br> + +<br> +Does this indicate a memory leak? +<br> + +<br> +Does someone have the tools to run some diagnostics? +<br> + +<br> +(NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again)

+
+

[FOR-713] HTML-to-document.xsl no longer generates an XDoc

@@ -284,7 +304,7 @@ <br>

- +

[FOR-762] Default page URL for breadcrumbs and site: links

@@ -316,26 +336,6 @@ <br> Cocoon does not appear to assume the end node directory is index.* and thus appends no file automatically as tomcat or the http server does so it must be manually done.

- -

[FOR-591] MaxMemory needs increasing

-
-

-http://issues.apache.org/jira/browse/FOR-591 -

-

Since the docs restructurng for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site. -<br> - -<br> -Does this indicate a memory leak? -<br> - -<br> -Does someone have the tools to run some diagnostics? -<br> - -<br> -(NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again)

-

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

@@ -360,7 +360,39 @@ <br>

- + +

[FOR-533] Auto Generate plugins.xml entry

+
+

+http://issues.apache.org/jira/browse/FOR-533 +

+

The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files. +<br> + +<br> +All the necessary values are now in the plugin build.xml file. +<br> + +<br> +This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap

+
+ +

[FOR-735] Plugins are not correctly deployed in webapp mode

+
+

+http://issues.apache.org/jira/browse/FOR-735 +

+

(At this point I didn't try this scenario step by step any more; basically it is what we did to setup the site, except that we copied our project data from forrest 0.6 before trying the pdf links) +<br> + +<br> +- run forrest webapp to create an empty webapp +<br> +- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory) +<br> +- the pdf links give an error &quot;Resource Not Found&quot;

+
+

[FOR-707] Document i18n features of Forrest

@@ -380,7 +412,7 @@ <br> We could, at the very least use the locationmap to pull this content into our site [OT: I wonder if this could be a way to generate more documentation?)

- +

[FOR-711] Cache results from the Locationmap

@@ -396,7 +428,7 @@ <br> If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701)

- +

[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo

@@ -410,38 +442,6 @@ <br> <a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a>

- -

[FOR-533] Auto Generate plugins.xml entry

-
-

-http://issues.apache.org/jira/browse/FOR-533 -

-

The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files. -<br> - -<br> -All the necessary values are now in the plugin build.xml file. -<br> - -<br> -This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap

-
- -

[FOR-735] Plugins are not correctly deployed in webapp mode

-
-

-http://issues.apache.org/jira/browse/FOR-735 -

-

(At this point I didn't try this scenario step by step any more; basically it is what we did to setup the site, except that we copied our project data from forrest 0.6 before trying the pdf links) -<br> - -<br> -- run forrest webapp to create an empty webapp -<br> -- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory) -<br> -- the pdf links give an error &quot;Resource Not Found&quot;

-

[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes

@@ -488,17 +488,7 @@ <br> the ampersand in the link href attribute is not.

- -

[FOR-210] whole-site html and pdf: broken link faq, broken image links

-
-

-http://issues.apache.org/jira/browse/FOR-210 -

-

The &quot;fresh-site&quot; build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue?<br> -<br> -

-
- +

[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs

@@ -512,6 +502,16 @@ <br>

+ +

[FOR-210] whole-site html and pdf: broken link faq, broken image links

+
+

+http://issues.apache.org/jira/browse/FOR-210 +

+

The &quot;fresh-site&quot; build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue?<br> +<br> +

+

[FOR-211] whole-site html and pdf: broken ext links

@@ -622,7 +622,19 @@ <br>

- + +

[FOR-644] whitespace cleanup

+
+

+http://issues.apache.org/jira/browse/FOR-644 +

+

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 see the list at trunk/etc/whitespace-cleanup.txt +<br> + +<br> +This Issue will be used to announce which section of the repository is due to be cleaned next. Please keep discussion on that mail thread.

+
+

[FOR-645] patches for whitespace cleanup

@@ -630,19 +642,19 @@

Use this issue to provide patches for the whitespace cleanup.

- -

[FOR-644] whitespace cleanup

+ +

[FOR-726] use locationmap in all of the plugins

-http://issues.apache.org/jira/browse/FOR-644 +http://issues.apache.org/jira/browse/FOR-726

-

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 see the list at trunk/etc/whitespace-cleanup.txt +

Each plugin has sitemaps that need to use the locationmap. <br> <br> -This Issue will be used to announce which section of the repository is due to be cleaned next. Please keep discussion on that mail thread.

+(Perhaps we need Jira sub-tasks for each plugin.)

- +

[FOR-721] entries without labels in site.xml are now being crawled and generated

@@ -654,7 +666,7 @@ <br> This is most likely a side-effect of the workaround for issue FOR-675

- +

[FOR-677] leading slash in gathered URIs causes double the number of links to be processed

@@ -674,41 +686,13 @@ <br> However, we do have a sitemap transformer to &quot;relativize&quot; and &quot;absolutize&quot; the links. Should it always trim the leading slash? Or are there cases where that should not happen, so cannot generalise?

- +

[FOR-699] Beginner HowTos for installing Forrest

http://issues.apache.org/jira/browse/FOR-699

These are a whole group of HowTos that I wrote for my local users (probably a tutorial would be a better format). They are not complete, nor tidied at this point, but they cover a lot of basic step-by-step stuff specifically geared towards Linux with Gnome desktop and Windows XP. Figured I would put them out there so we can pull out bits we may want to use.

-
- -

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

-
-

-http://issues.apache.org/jira/browse/FOR-705 -

-

Build fails when given target URL of rewriteDemo is not available (site down, no longer exists, incorrect URL typing etc). -<br> - -<br> -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] -<br> - -<br> -[1] <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112826350500282">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112826350500282</a> -<br> - -<br> -[2] <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=11270994920771">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=11270994920771</a> -<br> - -<br> -[3] <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112859428219336&w=2">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112859428219336&amp;w=2</a> -<br> - -<br> -