You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by th...@apache.org on 2007/01/15 00:16:43 UTC
svn commit: r496187 - in /forrest/site: ./ docs_0_80/ docs_0_80/howto/ dtdx/
images/ pluginDocs/plugins_0_70/ pluginDocs/plugins_0_80/
procedures/release/ skin/
Author: thorsten
Date: Sun Jan 14 15:16:41 2007
New Revision: 496187
URL: http://svn.apache.org/viewvc?view=rev&rev=496187
Log:
Automatic publish from forrestbot
Added:
forrest/site/images/ASF-us-2006-web_masthead.jpg (with props)
forrest/site/images/apache_con_asia_header.png (with props)
Modified:
forrest/site/committed-1.png
forrest/site/docs_0_80/howto/howto-buildPlugin.html
forrest/site/docs_0_80/howto/howto-buildPlugin.pdf
forrest/site/docs_0_80/linking.pdf
forrest/site/docs_0_80/primer.pdf
forrest/site/docs_0_80/your-project.pdf
forrest/site/dtdx/document-v12.pdf
forrest/site/dtdx/document-v13.pdf
forrest/site/dtdx/document-v20.pdf
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
forrest/site/pluginDocs/plugins_0_70/index.html
forrest/site/pluginDocs/plugins_0_70/index.pdf
forrest/site/pluginDocs/plugins_0_80/index.html
forrest/site/pluginDocs/plugins_0_80/index.pdf
forrest/site/procedures/release/announce_code_freeze.txt
forrest/site/procedures/release/announce_end_of_code_freeze.txt
forrest/site/procedures/release/announce_release.txt
forrest/site/procedures/release/propose_release_plan.txt
forrest/site/procedures/release/rc_did_not_build_what_now.txt
forrest/site/procedures/release/test_and_vote_on_rel_cand.txt
forrest/site/skin/basic.css
forrest/site/skin/print.css
forrest/site/skin/profile.css
Modified: forrest/site/committed-1.png
URL: http://svn.apache.org/viewvc/forrest/site/committed-1.png?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-buildPlugin.html?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/docs_0_80/howto/howto-buildPlugin.html (original)
+++ forrest/site/docs_0_80/howto/howto-buildPlugin.html Sun Jan 14 15:16:41 2007
@@ -818,7 +818,7 @@
<p>Dispatcher (previous codename Forrest Views) is the collective name for the various pieces of functionality
that are intended to replace skins in the future. They allow for a much more
configurable system of defining the contents and look and feel of a site.</p>
-<p>Plugins can expose contracts for use in structurer files used within
+<p>Plugins can expose contracts, resources and tiles for use in structurer files used within
Dispatcher-based sites. In order to do this you should develop your contracts
as normal and place them in <span class="codefrag">PLUGIN_HOME/resources/themes</span>. However,
this, by itself, is not sufficient to export your contracts. You will also need to
@@ -826,13 +826,25 @@
<pre class="code">
<match pattern="resolvePluginContract.*.**">
<select type="exists">
- <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:theme}/{1}/{2}.ft" />
+ <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:dispatcher.theme}/{1}/{2}.ft" />
+ <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:dispatcher.fallback.theme}/{1}/{2}.ft" />
</select>
</match>
- </pre>
+ <match pattern="resolvePluginThemes.*.**">
+ <select type="exists">
+ <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:dispatcher.theme}/{1}/{2}.{1}" />
+ <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:dispatcher.fallback.theme}/{1}/{2}.{1}" />
+ </select>
+ </match>
+ <match pattern="resolvePluginTiles.**">
+ <select type="exists">
+ <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:dispatcher.theme}/html/{1}.vt.xml" />
+ <location src="{forrest:forrest.plugins}/PLUGIN_NAME/resources/themes/{properties:dispatcher.fallback.theme}/html/{1}.vt.xml" />
+ </select>
+ </match></pre>
<p>Of course, you should replace <span class="codefrag">PLUGIN_NAME</span> with the name of
your plugin.</p>
-<p>Once Dispatcher becomes stable we will add this match to the default locationmap
+<p>Once Dispatcher becomes stable we will add this matches to the default locationmap
which is generated when you seed a new plugin, but for now it must be done manually.</p>
<a name="N1027D"></a><a name="Plugin+Properties"></a>
<h4>Plugin Properties</h4>
Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-buildPlugin.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/linking.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/linking.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/primer.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/primer.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/your-project.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/your-project.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/dtdx/document-v12.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v12.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/dtdx/document-v13.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/dtdx/document-v20.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v20.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sun Jan 14 15:16:41 2007
@@ -252,9 +252,6 @@
<a href="#%5BFOR-537%5D+Plugin+documentation+sitemap+references">[FOR-537] Plugin documentation sitemap references</a>
</li>
<li>
-<a href="#%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory">[FOR-635] images not reproduced in PDFs, if sources are in xdocs/images directory</a>
-</li>
-<li>
<a href="#%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning">[FOR-671] Layering error of HTML headings breaks rest of the page w/o warning</a>
</li>
<li>
@@ -263,6 +260,9 @@
<li>
<a href="#%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links">[FOR-767] Forrestbot webapp reports succesful even when there are broken links</a>
</li>
+<li>
+<a href="#%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files">[FOR-861] Update locationmap docs for working with remote files</a>
+</li>
</ul>
</div>
<div class="note">
@@ -279,20 +279,13 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-855">http://issues.apache.org/jira/browse/FOR-855</a>
</p>
-<p>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).
+<p>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/>
-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
+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/>
</p>
</div>
<a name="N1001D"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
@@ -301,7 +294,7 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-868">http://issues.apache.org/jira/browse/FOR-868</a>
</p>
-<p>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">FOR-865</a> &quot;Add missing entries to status.xml to generate the changes list&quot;.</p>
+<p>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">FOR-865</a> &quot;Add missing entries to status.xml to generate the changes list&quot;.</p>
</div>
<a name="N10029"></a><a name="%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
<h2 class="underlined_10">[FOR-865] Add missing entries to status.xml to generate the changes list</h2>
@@ -309,16 +302,11 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-865">http://issues.apache.org/jira/browse/FOR-865</a>
</p>
-<p>There are insufficient entries in our site-author/status.xml to generate the changes.html for the upcoming release.
+<p>There are insufficient entries in our site-author/status.xml to generate the changes.html for the upcoming release.<br/>
<br/>
-
-<br/>
-Besides informing users of the major changes and providing cross-links to the issue tracker, this file also provides recognition of contributions ... at the moment there are too few. It also has the importance=high attribute, which generates our release announcement ... again, too few.
-<br/>
-
-<br/>
-Re: better use of changes.html (Was: Community health)
+Besides informing users of the major changes and providing cross-links to the issue tracker, this file also provides recognition of contributions ... at the moment there are too few. It also has the importance=high attribute, which generates our release announcement ... again, too few.<br/>
<br/>
+Re: better use of changes.html (Was: Community health)<br/>
<a href="http://marc.theaimsgroup.com/?t=114274836600001">http://marc.theaimsgroup.com/?t=114274836600001</a></p>
</div>
<a name="N10035"></a><a name="%5BFOR-911%5D+decide+content+of+release"></a>
@@ -327,14 +315,10 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-911">http://issues.apache.org/jira/browse/FOR-911</a>
</p>
-<p>For past releases we have essentially done a &quot;source&quot; release, i.e. pack everything found in svn trunk including a pre-built forrest binary jar file.
-<br/>
-
-<br/>
-Here is one recent discussion:
-<br/>
-&nbsp;content of release [was: Re: review list of scheduled issues for 0.8 release]
+<p>For past releases we have essentially done a &quot;source&quot; release, i.e. pack everything found in svn trunk including a pre-built forrest binary jar file.<br/>
<br/>
+Here is one recent discussion:<br/>
+&nbsp;content of release [was: Re: review list of scheduled issues for 0.8 release]<br/>
&nbsp;<a href="http://marc.theaimsgroup.com/?t=115257903800001">http://marc.theaimsgroup.com/?t=115257903800001</a></p>
</div>
<a name="N10041"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
@@ -343,13 +327,9 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-533">http://issues.apache.org/jira/browse/FOR-533</a>
</p>
-<p>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/>
-
+<p>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/>
-
+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</p>
</div>
@@ -359,10 +339,8 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-639">http://issues.apache.org/jira/browse/FOR-639</a>
</p>
-<p>See the email thread:
-<br/>
-<a href="http://marc.theaimsgroup.com/?t=112276643700001">http://marc.theaimsgroup.com/?t=112276643700001</a>
-<br/>
+<p>See the email thread:<br/>
+<a href="http://marc.theaimsgroup.com/?t=112276643700001">http://marc.theaimsgroup.com/?t=112276643700001</a><br/>
</p>
</div>
<a name="N10059"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
@@ -371,14 +349,10 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-735">http://issues.apache.org/jira/browse/FOR-735</a>
</p>
-<p>(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)
+<p>(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;</p>
</div>
<a name="N10065"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
@@ -387,12 +361,9 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-742">http://issues.apache.org/jira/browse/FOR-742</a>
</p>
-<p>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:
+<p>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></p>
</div>
<a name="N10071"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
@@ -401,44 +372,25 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-241">http://issues.apache.org/jira/browse/FOR-241</a>
</p>
-<p>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>
+<p>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/>
-However, the generated HTML has the entity resolution UNDONE!:
+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/>
-<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>
+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
+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.</p>
</div>
<a name="N1007D"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
@@ -447,9 +399,7 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-200">http://issues.apache.org/jira/browse/FOR-200</a>
</p>
-<p>The locationmap gives us the ability to specify where sources are, both for Forrest and for the users.
-<br/>
-
+<p>The locationmap gives us the ability to specify where sources are, both for Forrest and for the users.<br/>
<br/>
Beware that it will not work for raw files that are not linked, as this &quot;feature&quot; currently uses a fixed dir being being copied by Ant.</p>
</div>
@@ -459,29 +409,17 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-546">http://issues.apache.org/jira/browse/FOR-546</a>
</p>
-<p>The example at <a href="http://forrest.apache.org/0.7/docs/sitemap-ref.html#pdf">http://forrest.apache.org/0.7/docs/sitemap-ref.html#pdf</a> uses a fo2pdf serializer. This probaly worked in versions &lt; 0.7, because the PDF output feature was in the core, and the serializer was very likely declared there.
-<br/>
-
-<br/>
-With version 0.7, PDF output is moved to a plugin, the fo2pdf serializer seems to be no longer there. The serializer should probably be added to the example, for completeness.
-<br/>
-
-<br/>
-&nbsp;&nbsp;&lt;map:components&gt;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&lt;map:serializers&gt;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;map:serializer name=&quot;fo2pdf&quot;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src=&quot;org.apache.cocoon.serialization.FOPSerializer&quot;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mime-type=&quot;application/pdf&quot;/&gt;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&lt;/map:serializers&gt;
+<p>The example at <a href="http://forrest.apache.org/0.7/docs/sitemap-ref.html#pdf">http://forrest.apache.org/0.7/docs/sitemap-ref.html#pdf</a> uses a fo2pdf serializer. This probaly worked in versions &lt; 0.7, because the PDF output feature was in the core, and the serializer was very likely declared there.<br/>
<br/>
-&nbsp;&nbsp;&lt;/map:components&gt;
+With version 0.7, PDF output is moved to a plugin, the fo2pdf serializer seems to be no longer there. The serializer should probably be added to the example, for completeness.<br/>
<br/>
-
+ &lt;map:components&gt;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&lt;map:serializers&gt;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;map:serializer name=&quot;fo2pdf&quot;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src=&quot;org.apache.cocoon.serialization.FOPSerializer&quot;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mime-type=&quot;application/pdf&quot;/&gt;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&lt;/map:serializers&gt;<br/>
+&nbsp;&nbsp;&lt;/map:components&gt;<br/>
<br/>
I found out about this because my sitemap uses the fo2pdf too (docbook to PDF), and had to add the serializer.</p>
</div>
@@ -491,8 +429,7 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-644">http://issues.apache.org/jira/browse/FOR-644</a>
</p>
-<p>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/>
+<p>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/>
</p>
</div>
<a name="N100A1"></a><a name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
@@ -501,13 +438,9 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-666">http://issues.apache.org/jira/browse/FOR-666</a>
</p>
-<p>The pattern matching example is quite misleading. There should be a note where exactly to copy your old site (in a standard seeded project) to make the pattern matching work.
-<br/>
-
+<p>The pattern matching example is quite misleading. There should be a note where exactly to copy your old site (in a standard seeded project) to make the pattern matching work.<br/>
<br/>
-At least for me it worked only after I used a **.html directeive.
-<br/>
-
+At least for me it worked only after I used a **.html directeive.<br/>
<br/>
&lt;map:match pattern=&quot;old_site/**.html&quot;&gt;</p>
</div>
@@ -517,9 +450,7 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-726">http://issues.apache.org/jira/browse/FOR-726</a>
</p>
-<p>Each plugin has sitemaps that need to use the locationmap.
-<br/>
-
+<p>Each plugin has sitemaps that need to use the locationmap.<br/>
<br/>
(Perhaps we need Jira sub-tasks for each plugin.)</p>
</div>
@@ -537,8 +468,7 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-901">http://issues.apache.org/jira/browse/FOR-901</a>
</p>
-<p>Review the note on the home page about first forrest run and retrieving plugins from network
-<br/>
+<p>Review the note on the home page about first forrest run and retrieving plugins from network<br/>
<a href="http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&r2=365494&pathrev=365495">http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&amp;r2=365494&amp;pathrev=365495</a></p>
</div>
<a name="N100D1"></a><a name="%5BFOR-906%5D+locationmap+documentation+explain+this-to-that.xsl+naming+convention+and+default+lm+matches"></a>
@@ -555,13 +485,9 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-922">http://issues.apache.org/jira/browse/FOR-922</a>
</p>
-<p>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/>
-
+<p>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/>
-
+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.</p>
</div>
@@ -571,25 +497,15 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-936">http://issues.apache.org/jira/browse/FOR-936</a>
</p>
-<p>When moving from one page to another and switching locales in between, the chosen locale is lost when entering the new page. To reproduce:
-<br/>
-
+<p>When moving from one page to another and switching locales in between, the chosen locale is lost when entering the new page. To reproduce:<br/>
<br/>
-1) set up and run forrest with i18n ON
+1) set up and run forrest with i18n ON<br/>
+2) open a localized page<br/>
+3) switch locale by appending '?locale=XY' in the address field<br/>
+4) open another page available in both the original locale (before the switch) and the new locale XY<br/>
+5) notice how the new page is displayed in the original locale, NOT the expected XY locale<br/>
<br/>
-2) open a localized page
-<br/>
-3) switch locale by appending '?locale=XY' in the address field
-<br/>
-4) open another page available in both the original locale (before the switch) and the new locale XY
-<br/>
-5) notice how the new page is displayed in the original locale, NOT the expected XY locale
-<br/>
-
-<br/>
-Although one could argue that the described behaviour is wanted in some cases, I believe that to most users it would be natural that the locale is &quot;sticky&quot; once changed - it should not change back by itself. Thus, the &quot;sticky&quot; behaviour should be default in Forrest.
-<br/>
-
+Although one could argue that the described behaviour is wanted in some cases, I believe that to most users it would be natural that the locale is &quot;sticky&quot; once changed - it should not change back by itself. Thus, the &quot;sticky&quot; behaviour should be default in Forrest.<br/>
<br/>
The fix is simple, patch to come soon.</p>
</div>
@@ -599,36 +515,21 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-704">http://issues.apache.org/jira/browse/FOR-704</a>
</p>
-<p>template for span-element traverses to children elements via xsl:apply-templates TWICE!
-<br/>
-once in xsl:choose, than outside
-<br/>
-thus producing doubling the content of span.
-<br/>
-::
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&lt;xsl:template match=&quot;span&quot;&gt;
-<br/>
- &lt;xsl:choose&gt;
-<br/>
-&lt;!-- ... --&gt;
-<br/>
- &lt;xsl:otherwise&gt;
-<br/>
- &lt;!-- Strip --&gt;
-<br/>
- &lt;xsl:apply-templates/&gt;
-<br/>
- &lt;/xsl:otherwise&gt;
-<br/>
- &lt;/xsl:choose&gt;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;xsl:apply-templates select=&quot;./*&quot;/&gt;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&lt;/xsl:template&gt;
-<br/>
+<p>template for span-element traverses to children elements via xsl:apply-templates TWICE!<br/>
+once in xsl:choose, than outside<br/>
+thus producing doubling the content of span.<br/>
+::<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&lt;xsl:template match=&quot;span&quot;&gt;<br/>
+ &lt;xsl:choose&gt;<br/>
+&lt;!-- ... --&gt;<br/>
+ &lt;xsl:otherwise&gt;<br/>
+ &lt;!-- Strip --&gt;<br/>
+ &lt;xsl:apply-templates/&gt;<br/>
+ &lt;/xsl:otherwise&gt;<br/>
+ &lt;/xsl:choose&gt;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;<br/>
+ &lt;xsl:apply-templates select=&quot;./*&quot;/&gt; <br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&lt;/xsl:template&gt;<br/>
</p>
</div>
<a name="N10101"></a><a name="%5BFOR-537%5D+Plugin+documentation+sitemap+references"></a>
@@ -637,125 +538,88 @@
<p>
<a href="http://issues.apache.org/jira/browse/FOR-537">http://issues.apache.org/jira/browse/FOR-537</a>
</p>
-<p>This one references:
-<br/>
-&quot;FORREST_INSTALL_DIR/plugins/sitemap.xmap&quot;
+<p>This one references:<br/>
+&quot;FORREST_INSTALL_DIR/plugins/sitemap.xmap&quot;<br/>
+and<br/>
+&quot;src/plugins/sitemap.xmap&quot;<br/>
+and<br/>
+&quot;&lt;map:mount uri-prefix=&quot;&quot;<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src=&quot;{forrest:plugins}/sitemap.xmap&quot;:<br/>
<br/>
-and
+<a href="http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F">http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F</a><br/>
<br/>
-&quot;src/plugins/sitemap.xmap&quot;
-<br/>
-and
-<br/>
-&quot;&lt;map:mount uri-prefix=&quot;&quot;
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src=&quot;{forrest:plugins}/sitemap.xmap&quot;:
-<br/>
-
-<br/>
-<a href="http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F">http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F</a>
-<br/>
-
-<br/>
-
<br/>
--tim</p>
</div>
-<a name="N1010D"></a><a name="%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory"></a>
-<h2 class="underlined_10">[FOR-635] images not reproduced in PDFs, if sources are in xdocs/images directory</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-635">http://issues.apache.org/jira/browse/FOR-635</a>
-</p>
-<p>We used to enable images to be placed in the xdocs/images directory. However, now they are intended to go in the resources/images directory instead. Both methods will work for html pages, but only the latter method for the PDF pages.</p>
-</div>
-<a name="N10119"></a><a name="%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning"></a>
+<a name="N1010D"></a><a name="%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning"></a>
<h2 class="underlined_10">[FOR-671] Layering error of HTML headings breaks rest of the page w/o warning</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-671">http://issues.apache.org/jira/browse/FOR-671</a>
</p>
-<p>Up to revision 280144 if you make Forrest display the following file as a skinned .html-file in Forrest, you'll only see the title. Only if you fix the layering error of the headings and make h2 into h1 will the rest of the page content show.
-<br/>
-
-<br/>
-If Forrest minds this layering error it should at least report it as an error, shoulnd't it?
-<br/>
-
-<br/>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;ISO-8859-1&quot;?&gt;
+<p>Up to revision 280144 if you make Forrest display the following file as a skinned .html-file in Forrest, you'll only see the title. Only if you fix the layering error of the headings and make h2 into h1 will the rest of the page content show.<br/>
<br/>
-&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0 Strict//EN&quot; &quot;<a href="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</a>&quot;&gt;
-<br/>
-&lt;html&gt;
-<br/>
-&lt;head&gt;
-<br/>
-&lt;title&gt;Englisch&lt;/title&gt;
-<br/>
-&lt;/head&gt;
-<br/>
-&lt;body class=&quot;Oberbereich&quot;&gt;
-<br/>
-&lt;h2&gt;Kursthemen&lt;/h2&gt;
-<br/>
-&lt;ul class=&quot;Kursthemenliste&quot;&gt;
-<br/>
-&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;
-<br/>
-&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot; href=&quot;$KursthemaDateiname&quot;&gt;Getting Started in Business (Abendkurs 1 x w&#xF6;chentlich)
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;
-<br/>
-&lt;/li&gt;
-<br/>
-&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;
-<br/>
-&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot; href=&quot;$KursthemaDateiname&quot;&gt;Getting Ahead in Business (Abendkurs 1 x w&#xF6;chentlich)
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;
-<br/>
-&lt;/li&gt;
-<br/>
-&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;
-<br/>
-&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot; href=&quot;$KursthemaDateiname&quot;&gt;Complaints, Reports and other Messages (Wochenendseminar)
-<br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;
-<br/>
-&lt;/li&gt;
-<br/>
-&lt;/ul&gt;
-<br/>
-&lt;/body&gt;
+If Forrest minds this layering error it should at least report it as an error, shoulnd't it?<br/>
<br/>
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;ISO-8859-1&quot;?&gt;<br/>
+&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0 Strict//EN&quot; &quot;<a href="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</a>&quot;&gt;<br/>
+&lt;html&gt;<br/>
+&lt;head&gt;<br/>
+&lt;title&gt;Englisch&lt;/title&gt;<br/>
+&lt;/head&gt;<br/>
+&lt;body class=&quot;Oberbereich&quot;&gt;<br/>
+&lt;h2&gt;Kursthemen&lt;/h2&gt;<br/>
+&lt;ul class=&quot;Kursthemenliste&quot;&gt;<br/>
+&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;<br/>
+&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot; href=&quot;$KursthemaDateiname&quot;&gt;Getting Started in Business (Abendkurs 1 x w&#xF6;chentlich)<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;<br/>
+&lt;/li&gt;<br/>
+&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;<br/>
+&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot; href=&quot;$KursthemaDateiname&quot;&gt;Getting Ahead in Business (Abendkurs 1 x w&#xF6;chentlich)<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;<br/>
+&lt;/li&gt;<br/>
+&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;<br/>
+&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot; href=&quot;$KursthemaDateiname&quot;&gt;Complaints, Reports and other Messages (Wochenendseminar)<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;<br/>
+&lt;/li&gt;<br/>
+&lt;/ul&gt;<br/>
+&lt;/body&gt;<br/>
&lt;/html&gt;</p>
</div>
-<a name="N10125"></a><a name="%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675"></a>
+<a name="N10119"></a><a name="%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675"></a>
<h2 class="underlined_10">[FOR-731] empty linkmap.html document, side-effect of workaround to FOR-675</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-731">http://issues.apache.org/jira/browse/FOR-731</a>
</p>
-<p>The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a workaround for a side-effect to the of the workaround for issue <a href="http://issues.apache.org/jira/browse/FOR-675" title="upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.">FOR-675</a>.</p>
+<p>The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a workaround for a side-effect to the of the workaround for issue <a href="https://issues.apache.org/jira/browse/FOR-675" title="upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.">FOR-675</a>.</p>
</div>
-<a name="N10131"></a><a name="%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links"></a>
+<a name="N10125"></a><a name="%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links"></a>
<h2 class="underlined_10">[FOR-767] Forrestbot webapp reports succesful even when there are broken links</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-767">http://issues.apache.org/jira/browse/FOR-767</a>
</p>
-<p>We should also report why it failed:
-<br/>
-
+<p>We should also report why it failed:<br/>
<br/>
-- plugin problem
-<br/>
-- broken link (with a link to the broken links file)
+- plugin problem<br/>
+- broken link (with a link to the broken links file)<br/>
+- ??<br/>
+</p>
+</div>
+<a name="N10131"></a><a name="%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files"></a>
+<h2 class="underlined_10">[FOR-861] Update locationmap docs for working with remote files</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-861">http://issues.apache.org/jira/browse/FOR-861</a>
+</p>
+<p>The docs for retrieving content from remote locations [1] have not kept up with Tims wonderful naming conventions for the locationmap [2]<br/>
<br/>
-- ??
+We need to update the docs to reflect the situation described in [3] (don't miss the correction in the next message)<br/>
<br/>
-</p>
+[1] <a href="http://forrest.apache.org/docs_0_80/locationmap.html#source-via-http">http://forrest.apache.org/docs_0_80/locationmap.html#source-via-http</a><br/>
+[2] <a href="http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention">http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention</a><br/>
+[3] <a href="http://marc.theaimsgroup.com/?t=114492612100001&r=1&w=2">http://marc.theaimsgroup.com/?t=114492612100001&amp;r=1&amp;w=2</a></p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Added: forrest/site/images/ASF-us-2006-web_masthead.jpg
URL: http://svn.apache.org/viewvc/forrest/site/images/ASF-us-2006-web_masthead.jpg?view=auto&rev=496187
==============================================================================
Binary file - no diff available.
Propchange: forrest/site/images/ASF-us-2006-web_masthead.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added: forrest/site/images/apache_con_asia_header.png
URL: http://svn.apache.org/viewvc/forrest/site/images/apache_con_asia_header.png?view=auto&rev=496187
==============================================================================
Binary file - no diff available.
Propchange: forrest/site/images/apache_con_asia_header.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Modified: forrest/site/pluginDocs/plugins_0_70/index.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_70/index.html?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/index.html Sun Jan 14 15:16:41 2007
@@ -184,7 +184,7 @@
<a href="#Output+Plugins-N10469">Output Plugins</a>
</li>
<li>
-<a href="#Internal+Plugins-N10555">Internal Plugins</a>
+<a href="#Internal+Plugins-N10583">Internal Plugins</a>
</li>
</ul>
</li>
@@ -1015,7 +1015,35 @@
</th><td>0.7</td>
</tr>
</table>
-<a name="N104F9"></a><a name="org.apache.forrest.plugin.output.voice"></a>
+<a name="N104F9"></a><a name="org.apache.forrest.plugin.output.solr"></a>
+<h5>org.apache.forrest.plugin.output.solr</h5>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+<tr>
+<th width="25%">Description</th><td>
+<p> Generates solr documents from xdos. Further when run with the dispatcher
+ it provides a GUI to manage your project in solr and a search interface to search your solr
+ server. </p>
+</td>
+</tr>
+<tr>
+<th width="25%">Author</th><td>Apache Forrest Project</td>
+</tr>
+<tr>
+<th width="25%">Website</th><td><a href="http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.solr">http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.solr</a></td>
+</tr>
+<tr>
+<th width="25%">Download URL:</th><td><a href="http://forrest.apache.org/plugins/">http://forrest.apache.org/plugins/</a></td>
+</tr>
+<tr>
+<th width="25%">Latest Plugin version</th><td>0.1</td>
+</tr>
+<tr>
+<th width="25%">
+ Minimum Forrest version required *
+ </th><td>0.8</td>
+</tr>
+</table>
+<a name="N10527"></a><a name="org.apache.forrest.plugin.output.voice"></a>
<h5>org.apache.forrest.plugin.output.voice</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1044,7 +1072,7 @@
</th><td>0.8</td>
</tr>
</table>
-<a name="N10527"></a><a name="org.apache.forrest.themes.core"></a>
+<a name="N10555"></a><a name="org.apache.forrest.themes.core"></a>
<h5>org.apache.forrest.themes.core</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1072,13 +1100,13 @@
</th><td>0.8</td>
</tr>
</table>
-<a name="N10555"></a><a name="Internal+Plugins-N10555"></a>
+<a name="N10583"></a><a name="Internal+Plugins-N10583"></a>
<h4>Internal Plugins</h4>
<p>
Internal plugins change the core behaviour
of Forrest.
</p>
-<a name="N1055B"></a><a name="org.apache.forrest.plugin.internal.dispatcher"></a>
+<a name="N10589"></a><a name="org.apache.forrest.plugin.internal.dispatcher"></a>
<h5>org.apache.forrest.plugin.internal.dispatcher</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1106,7 +1134,7 @@
</th><td>0.8</td>
</tr>
</table>
-<a name="N10589"></a><a name="org.apache.forrest.plugin.internal.IMSManifest"></a>
+<a name="N105B7"></a><a name="org.apache.forrest.plugin.internal.IMSManifest"></a>
<h5>org.apache.forrest.plugin.internal.IMSManifest</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1137,7 +1165,7 @@
</th><td>0.7</td>
</tr>
</table>
-<a name="N105B7"></a><a name="org.apache.forrest.plugin.internal.NoteTaking"></a>
+<a name="N105E5"></a><a name="org.apache.forrest.plugin.internal.NoteTaking"></a>
<h5>org.apache.forrest.plugin.internal.NoteTaking</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
Modified: forrest/site/pluginDocs/plugins_0_70/index.pdf
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_70/index.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/index.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/index.html?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/index.html Sun Jan 14 15:16:41 2007
@@ -184,7 +184,7 @@
<a href="#Output+Plugins-N10469">Output Plugins</a>
</li>
<li>
-<a href="#Internal+Plugins-N10555">Internal Plugins</a>
+<a href="#Internal+Plugins-N10583">Internal Plugins</a>
</li>
</ul>
</li>
@@ -1015,7 +1015,35 @@
</th><td>0.7</td>
</tr>
</table>
-<a name="N104F9"></a><a name="org.apache.forrest.plugin.output.voice"></a>
+<a name="N104F9"></a><a name="org.apache.forrest.plugin.output.solr"></a>
+<h5>org.apache.forrest.plugin.output.solr</h5>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+<tr>
+<th width="25%">Description</th><td>
+<p> Generates solr documents from xdos. Further when run with the dispatcher
+ it provides a GUI to manage your project in solr and a search interface to search your solr
+ server. </p>
+</td>
+</tr>
+<tr>
+<th width="25%">Author</th><td>Apache Forrest Project</td>
+</tr>
+<tr>
+<th width="25%">Website</th><td><a href="http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.solr">http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.solr</a></td>
+</tr>
+<tr>
+<th width="25%">Download URL:</th><td><a href="http://forrest.apache.org/plugins/">http://forrest.apache.org/plugins/</a></td>
+</tr>
+<tr>
+<th width="25%">Latest Plugin version</th><td>0.1</td>
+</tr>
+<tr>
+<th width="25%">
+ Minimum Forrest version required *
+ </th><td>0.8</td>
+</tr>
+</table>
+<a name="N10527"></a><a name="org.apache.forrest.plugin.output.voice"></a>
<h5>org.apache.forrest.plugin.output.voice</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1044,7 +1072,7 @@
</th><td>0.8</td>
</tr>
</table>
-<a name="N10527"></a><a name="org.apache.forrest.themes.core"></a>
+<a name="N10555"></a><a name="org.apache.forrest.themes.core"></a>
<h5>org.apache.forrest.themes.core</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1072,13 +1100,13 @@
</th><td>0.8</td>
</tr>
</table>
-<a name="N10555"></a><a name="Internal+Plugins-N10555"></a>
+<a name="N10583"></a><a name="Internal+Plugins-N10583"></a>
<h4>Internal Plugins</h4>
<p>
Internal plugins change the core behaviour
of Forrest.
</p>
-<a name="N1055B"></a><a name="org.apache.forrest.plugin.internal.dispatcher"></a>
+<a name="N10589"></a><a name="org.apache.forrest.plugin.internal.dispatcher"></a>
<h5>org.apache.forrest.plugin.internal.dispatcher</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1106,7 +1134,7 @@
</th><td>0.8</td>
</tr>
</table>
-<a name="N10589"></a><a name="org.apache.forrest.plugin.internal.IMSManifest"></a>
+<a name="N105B7"></a><a name="org.apache.forrest.plugin.internal.IMSManifest"></a>
<h5>org.apache.forrest.plugin.internal.IMSManifest</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -1137,7 +1165,7 @@
</th><td>0.7</td>
</tr>
</table>
-<a name="N105B7"></a><a name="org.apache.forrest.plugin.internal.NoteTaking"></a>
+<a name="N105E5"></a><a name="org.apache.forrest.plugin.internal.NoteTaking"></a>
<h5>org.apache.forrest.plugin.internal.NoteTaking</h5>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
Modified: forrest/site/pluginDocs/plugins_0_80/index.pdf
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/index.pdf?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
Binary files - no diff available.
Modified: forrest/site/procedures/release/announce_code_freeze.txt
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/announce_code_freeze.txt?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/procedures/release/announce_code_freeze.txt (original)
+++ forrest/site/procedures/release/announce_code_freeze.txt Sun Jan 14 15:16:41 2007
@@ -2,39 +2,39 @@
Table Of Contents
=================
-Subject: [Important] code-freeze commenced
-
-The code-freeze is now happening to allow us to pack the
-release candidates and make them available for testing.
-
-Code-freeze means *no* non-essential commits to the trunk
-or to the new release branch. Other branches are free to
-continue.
-
-There should be no code enhancements or new functionality,
-because that could introduce new bugs.
-
-The main aim is to find and fix important bugs. Any minor
-issues are delayed until after release (add to Jira).
-
-Documentation corrections can happen because they will not
-break anything. As long as we do test the documentation
-building just prior to making the final release candidate.
-
-However, if there are important code changes that are
-required you can make a proposal to allow that commit.
-The Release Manager will make a quick decision.
-
-Next important milestones are:
-
-* Create release candidate #2 if there have been changes
- on [date]
- [www.timeanddate.com-URL]
-
-* Actual release date is [date]
- [www.timeanddate.com-URL]
-
-Now we will go and build the releases which might take
-some time. The next message will tell you where to get
+Subject: [Important] code-freeze commenced
+
+The code-freeze is now happening to allow us to pack the
+release candidates and make them available for testing.
+
+Code-freeze means *no* non-essential commits to the trunk
+or to the new release branch. Other branches are free to
+continue.
+
+There should be no code enhancements or new functionality,
+because that could introduce new bugs.
+
+The main aim is to find and fix important bugs. Any minor
+issues are delayed until after release (add to Jira).
+
+Documentation corrections can happen because they will not
+break anything. As long as we do test the documentation
+building just prior to making the final release candidate.
+
+However, if there are important code changes that are
+required you can make a proposal to allow that commit.
+The Release Manager will make a quick decision.
+
+Next important milestones are:
+
+* Create release candidate #2 if there have been changes
+ on [date]
+ [www.timeanddate.com-URL]
+
+* Actual release date is [date]
+ [www.timeanddate.com-URL]
+
+Now we will go and build the releases which might take
+some time. The next message will tell you where to get
the release candidates and describe how to test.
Modified: forrest/site/procedures/release/announce_end_of_code_freeze.txt
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/announce_end_of_code_freeze.txt?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/procedures/release/announce_end_of_code_freeze.txt (original)
+++ forrest/site/procedures/release/announce_end_of_code_freeze.txt Sun Jan 14 15:16:41 2007
@@ -2,8 +2,8 @@
Table Of Contents
=================
-Subject: [Important] End of code-freeze
-
-The code-freeze has ended.
+Subject: [Important] End of code-freeze
+
+The code-freeze has ended.
Modified: forrest/site/procedures/release/announce_release.txt
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/announce_release.txt?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/procedures/release/announce_release.txt (original)
+++ forrest/site/procedures/release/announce_release.txt Sun Jan 14 15:16:41 2007
@@ -2,12 +2,12 @@
Table Of Contents
=================
-To: dev@forrest.apache.org,user@forrest.apache.org,announce@apache.org,announcements@xml.apache.org
-Subject: [Announce] Apache Forrest X.Y.Z
-
- !! Always refer them to the mirror facility
- !! Never mention the URL www.apache.org/ dist/ in email or web pages.
- Use the template at etc/announcement.txt
- Use your spelling checker!
+To: dev@forrest.apache.org,user@forrest.apache.org,announce@apache.org,announcements@xml.apache.org
+Subject: [Announce] Apache Forrest X.Y.Z
+
+ !! Always refer them to the mirror facility
+ !! Never mention the URL www.apache.org/ dist/ in email or web pages.
+ Use the template at etc/announcement.txt
+ Use your spelling checker!
Sign the email (e.g. GPG) if possible.
Modified: forrest/site/procedures/release/propose_release_plan.txt
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/propose_release_plan.txt?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/procedures/release/propose_release_plan.txt (original)
+++ forrest/site/procedures/release/propose_release_plan.txt Sun Jan 14 15:16:41 2007
@@ -2,55 +2,55 @@
Table Of Contents
=================
-FIXME: http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html
-incorporate that into this
-
-Subject: [VOTE] Release Plan for Forrest x.xx
-
-We are about to work on releasing a new version of Forrest.
-Below I have proposed the important milestones.
-
-Please check with your time schedules and comment.
-We want to have as many people available as possible
-to test the release candidate. So we can adjust the
-time schedule a bit.
-
-Please vote on this release plan.
+FIXME: http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html
+incorporate that into this
+
+Subject: [VOTE] Release Plan for Forrest x.xx
+
+We are about to work on releasing a new version of Forrest.
+Below I have proposed the important milestones.
+
+Please check with your time schedules and comment.
+We want to have as many people available as possible
+to test the release candidate. So we can adjust the
+time schedule a bit.
+
+Please vote on this release plan.
+
+Proposed Java version to test this release is [Version].
+
+Proposed milestones are:
+
+- Start of code-freeze on [Date]
+ [www.timeanddate.com-URL]
+
+- Start of test-period [Date]
+ [www.timeanddate.com-URL]
+
+- Vote on release candidate #1 [Date]
+ [www.timeanddate.com-URL]
+
+- Start of test-period [Date]
+ [www.timeanddate.com-URL]
+
+- Vote on release candidate [Date]
+ [www.timeanddate.com-URL]
+
+- If there are bugs in RC1
+
+ = Creation of release candidate #2
+ (only when there are bugs) [Date]
+ [www.timeanddate.com-URL]
+
+ = Start of test-period #2 [Date]
+ [www.timeanddate.com-URL]
-Proposed Java version to test this release is [Version].
-
-Proposed milestones are:
-
-- Start of code-freeze on [Date]
- [www.timeanddate.com-URL]
-
-- Start of test-period [Date]
- [www.timeanddate.com-URL]
-
-- Vote on release candidate #1 [Date]
- [www.timeanddate.com-URL]
-
-- Start of test-period [Date]
- [www.timeanddate.com-URL]
-
-- Vote on release candidate [Date]
- [www.timeanddate.com-URL]
-
-- If there are bugs in RC1
-
- = Creation of release candidate #2
- (only when there are bugs) [Date]
- [www.timeanddate.com-URL]
-
- = Start of test-period #2 [Date]
- [www.timeanddate.com-URL]
-
- = Vote on release candidate #2 [Date]
- [www.timeanddate.com-URL]
-
-- Scheduled release Date [Date]
- [www.timeanddate.com-URL]
-
-For background info on this step and the release process in general see
+ = Vote on release candidate #2 [Date]
+ [www.timeanddate.com-URL]
+
+- Scheduled release Date [Date]
+ [www.timeanddate.com-URL]
+
+For background info on this step and the release process in general see
http://forrest.apache.org/procedures/release/How_to_release.html#PrepRelPlan
Modified: forrest/site/procedures/release/rc_did_not_build_what_now.txt
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/rc_did_not_build_what_now.txt?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/procedures/release/rc_did_not_build_what_now.txt (original)
+++ forrest/site/procedures/release/rc_did_not_build_what_now.txt Sun Jan 14 15:16:41 2007
@@ -2,13 +2,13 @@
Table Of Contents
=================
-Subject: [Important] Release Candidate did NOT build, what now?
-
-The release candidate/documentation for the new release failed the tests.
-A quick attempt at to solve the problems has failed.
-
-What shall we do now?
-
-If anybody can suggest a solution please do, otherwise we will have to abort
+Subject: [Important] Release Candidate did NOT build, what now?
+
+The release candidate/documentation for the new release failed the tests.
+A quick attempt at to solve the problems has failed.
+
+What shall we do now?
+
+If anybody can suggest a solution please do, otherwise we will have to abort
this release attempt for now and write up a new release plan.
Modified: forrest/site/procedures/release/test_and_vote_on_rel_cand.txt
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/test_and_vote_on_rel_cand.txt?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/procedures/release/test_and_vote_on_rel_cand.txt (original)
+++ forrest/site/procedures/release/test_and_vote_on_rel_cand.txt Sun Jan 14 15:16:41 2007
@@ -2,64 +2,64 @@
Table Of Contents
=================
-Subject: [Important] please test release candidate then vote
-
-We need people to test the release candidate on your projects,
-especially on different operating systems. Just send a short
-reply to this thread that it works for you. See method below.
-
-Download the release candidate and supporting files:
-http://people.apache.org/~[your apache user name]/release-forrest-07/
-
-For Windows get *.zip md5sum ################################
-For UNIX get *.tar.gz md5sum ################################
-Get the *.asc and *.md5 that match your chosen download.
-
-It was packed from SVN revision ####
-Java [JavaVersion] or later is required.
-
-If you want to verify the download, then follow:
-http://forrest.apache.org/mirrors.cgi#verify
-
-Otherwise just get on with testing.
-
-Testing and vote period concludes [Date]
-Anyone can test and vote, not just PMC members.
-However only the PMC votes are binding.
-When voting, quote the md5sum to ensure that we are all
-using the correct release candidate.
-
-So we have approximately 6 days.
-
-Here are some hints:
-
- * Ensure that the compressed archive will unpack properly.
- * Verfiy the release, especially if you are a committer.
- * Follow the README.txt and index.html
- * Set $FORREST_HOME and $PATH appropriately.
- * Many known issues are already recorded at our Jira.
- * Don't worry too much about minor bugs. We are looking
- for blockers, such as it will not run.
- * Please add minor issues to Jira.
-
-* Make a fresh site ...
- cd my-new-dir
- forrest seed
- forrest run ... use the local jetty server.
- forrest ... build the whole site from the command-line.
- forrest war ... use your own full Jetty or Tomcat.
-
-* Try it on the Forrest core docs ...
- cd site-author
- forrest run
- forrest
-
-* Forrest was already pre-built. Try building it again.
- cd main
- build clean
- build
- build test
-
-* Try it on your own project, especially if you have
+Subject: [Important] please test release candidate then vote
+
+We need people to test the release candidate on your projects,
+especially on different operating systems. Just send a short
+reply to this thread that it works for you. See method below.
+
+Download the release candidate and supporting files:
+http://people.apache.org/~[your apache user name]/release-forrest-07/
+
+For Windows get *.zip md5sum ################################
+For UNIX get *.tar.gz md5sum ################################
+Get the *.asc and *.md5 that match your chosen download.
+
+It was packed from SVN revision ####
+Java [JavaVersion] or later is required.
+
+If you want to verify the download, then follow:
+http://forrest.apache.org/mirrors.cgi#verify
+
+Otherwise just get on with testing.
+
+Testing and vote period concludes [Date]
+Anyone can test and vote, not just PMC members.
+However only the PMC votes are binding.
+When voting, quote the md5sum to ensure that we are all
+using the correct release candidate.
+
+So we have approximately 6 days.
+
+Here are some hints:
+
+ * Ensure that the compressed archive will unpack properly.
+ * Verfiy the release, especially if you are a committer.
+ * Follow the README.txt and index.html
+ * Set $FORREST_HOME and $PATH appropriately.
+ * Many known issues are already recorded at our Jira.
+ * Don't worry too much about minor bugs. We are looking
+ for blockers, such as it will not run.
+ * Please add minor issues to Jira.
+
+* Make a fresh site ...
+ cd my-new-dir
+ forrest seed
+ forrest run ... use the local jetty server.
+ forrest ... build the whole site from the command-line.
+ forrest war ... use your own full Jetty or Tomcat.
+
+* Try it on the Forrest core docs ...
+ cd site-author
+ forrest run
+ forrest
+
+* Forrest was already pre-built. Try building it again.
+ cd main
+ build clean
+ build
+ build test
+
+* Try it on your own project, especially if you have
a project sitemap and use some extra plugins.
Modified: forrest/site/skin/basic.css
URL: http://svn.apache.org/viewvc/forrest/site/skin/basic.css?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/skin/basic.css (original)
+++ forrest/site/skin/basic.css Sun Jan 14 15:16:41 2007
@@ -163,4 +163,4 @@
.codefrag {
font-family: "Courier New", Courier, monospace;
font-size: 110%;
-}
+}
\ No newline at end of file
Modified: forrest/site/skin/print.css
URL: http://svn.apache.org/viewvc/forrest/site/skin/print.css?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/skin/print.css (original)
+++ forrest/site/skin/print.css Sun Jan 14 15:16:41 2007
@@ -51,4 +51,4 @@
acronym {
border: 0;
-}
+}
\ No newline at end of file
Modified: forrest/site/skin/profile.css
URL: http://svn.apache.org/viewvc/forrest/site/skin/profile.css?view=diff&rev=496187&r1=496186&r2=496187
==============================================================================
--- forrest/site/skin/profile.css (original)
+++ forrest/site/skin/profile.css Sun Jan 14 15:16:41 2007
@@ -150,4 +150,4 @@
/* extra-css */
#footer a { color: #0F3660; }
#footer a:visited { color: #009999; }
-
+
\ No newline at end of file