apache > forrest
 
 
PDF -icon
PDF
Font size:      

Open issues for the next release

Note
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-868] add relevant notes to the "Upgrading" xdoc

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

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="https://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-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo

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

The plugin retrieval and deployment process are not quite correct. Recently the projectInfo plugin had its version number incremented and the &quot;unversioned&quot; plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant plugin.<br/> <br/> The solution is discussed here:<br/> <a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a>

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

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

If I have a url like this inside the XML source:<br/> <br/> <a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a><br/> <br/> validate-xdocs fails because it wants the literal &amp; to be typed out as<br/> &amp; instead. So I correct it to become:<br/> <br/> <a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a><br/> <br/> However, the generated HTML has the entity resolution UNDONE!:<br/> <br/> <a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a><br/> <br/> This HTML fails validation as 4.01 transitional.<br/> <br/> David Crossley adds:<br/> There is a demonstration of the problem in the document<br/> src/documentation/content/xdocs/docs/dreams.xml<br/> The ampersand in the link element text is properly handled but<br/> the ampersand in the link href attribute is not.

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

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

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-644] code-style cleanup for xml files

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 <a href="http://marc.theaimsgroup.com/?t=112495618800002">http://marc.theaimsgroup.com/?t=112495618800002</a> and various linked discussions.<br/>