Return-Path: 
 <svn-return-4599-apmail-forrest-svn-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-svn-archive@www.apache.org
Received: (qmail 6783 invoked from network); 22 Dec 2005 01:41:43 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 22 Dec 2005 01:41:43 -0000
Received: (qmail 70184 invoked by uid 500); 22 Dec 2005 01:41:40 -0000
Delivered-To: apmail-forrest-svn-archive@forrest.apache.org
Received: (qmail 70114 invoked by uid 500); 22 Dec 2005 01:41:40 -0000
Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:svn-help@forrest.apache.org>
list-unsubscribe: <mailto:svn-unsubscribe@forrest.apache.org>
List-Post: <mailto:svn@forrest.apache.org>
Reply-To: "Forrest Developers List" <dev@forrest.apache.org>
List-Id: <svn.forrest.apache.org>
Delivered-To: mailing list svn@forrest.apache.org
Received: (qmail 70088 invoked by uid 99); 22 Dec 2005 01:41:40 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2005 17:41:40 -0800
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
	tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194)
    by apache.org (qpsmtpd/0.29) with SMTP; Wed, 21 Dec 2005 17:41:38 -0800
Received: (qmail 6613 invoked by uid 65534); 22 Dec 2005 01:41:18 -0000
Message-ID: <20051222014118.6610.qmail@minotaur.apache.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r358435 - in /forrest/site:
 docs_0_80/howto/howto-structurer-dsl.html
 docs_0_80/howto/howto-structurer-dsl.pdf forrest-issues.html
 forrest-issues.pdf guidelines.html guidelines.pdf
Date: Thu, 22 Dec 2005 01:41:17 -0000
To: svn@forrest.apache.org
From: crossley@apache.org
X-Mailer: svnmailer-1.0.5
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Author: crossley
Date: Wed Dec 21 17:41:04 2005
New Revision: 358435

URL: http://svn.apache.org/viewcvs?rev=358435&view=rev
Log:
Automatic publish from forrestbot

Modified:
    forrest/site/docs_0_80/howto/howto-structurer-dsl.html
    forrest/site/docs_0_80/howto/howto-structurer-dsl.pdf
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf
    forrest/site/guidelines.html
    forrest/site/guidelines.pdf

Modified: forrest/site/docs_0_80/howto/howto-structurer-dsl.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-structurer-dsl.html?rev=358435&r1=358434&r2=358435&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-structurer-dsl.html (original)
+++ forrest/site/docs_0_80/howto/howto-structurer-dsl.html Wed Dec 21 17:41:04 2005
@@ -358,6 +358,9 @@
 <li>
 <a href="#cssstructurer">CSS in the structurer</a>
 </li>
+<li>
+<a href="#Linking+to+an+external+css+file">Linking to an external css file</a>
+</li>
 </ul>
 </li>
 <li>
@@ -774,13 +777,62 @@
       </pre>
 <p> We are now able to place contracts into the layout container and add 
         custom css to the structurer. </p>
+<a name="N1015C"></a><a name="Linking+to+an+external+css+file"></a>
+<h3 class="underlined_5">Linking to an external css file</h3>
+<div class="note">
+<div class="label">Note</div>
+<div class="content">This will change for the next version of views (v3) where we use a 
+        generic contract instead of the standalone element (forrest:css). </div>
+</div>
+<p>Make sure your project has the following directory structure. If it 
+        doesn't you'll have to create it. "common" is the fallback for all 
+        themes, if you want to override the css for a specific theme replace 
+        "common" with "themeName". This is where Forrest will look for external 
+        css stylesheets. </p>
+<pre class="code">
+        $projectHome\src\documentation\resources\themes\common\css</pre>
+<p>Where $projectHome is the directory where your project exists.</p>
+<p>Put your css stylesheets in this directory. For arguement's sake let's say 
+        it's called mystyles.css</p>
+<p>Edit your common.fv structurer (or whatever structurer (theme) you are using). This 
+        will probably be some where in: </p>
+<pre class="code">$projectHome\src\documentation\content\xdocs</pre>
+<p>or if you want to override it for the whole project in:</p>
+<pre class="code">$projectHome\src\documentation\resources\themes\</pre>
+<p>Add the following element to the *.fv file:</p>
+<pre class="code">&lt;forrest:css url="styles.css" media="screen" theme="pelt"/&gt;
+        </pre>
+<p>
+<strong>Important!</strong> This must appear straight after the "view 
+        type" element (as first child): </p>
+<pre class="code">&lt;forrest:view type="html"&gt;</pre>
+<pre class="code">&lt;forrest:css url="mystyles.css" media="screen" theme="pelt"/&gt;
+        </pre>
+<p>The attributes are: </p>
+<ol>
+        
+<li>the url where the css exist (NOTE: it will be rewritten to "../themes/mystyles.css").</li>
+        
+<li>the media type, you can set different styles for screen and print. 
+          This is really useful if you want to hide elements such as navigation 
+          in the print output (#nav-section{display:none} for example).</li>
+        
+<li>the theme, "pelt" is the default theme (another is the "common" theme). Change this if you 
+          are using your own theme.</li>
+      
+</ol>
+<p>You can have as many css links as you like, and they'll appear in the 
+        head of your document in same order as they are in the .fv file.</p>
 <div class="fixme">
 <div class="label">Fixme (thorsten)</div>
-<div class="content"> Add more information of recent threads around css in the structurer 
-        </div>
+<div class="content"> Add more information of recent threads around 
+        css in the structurer and information how you add an @import? Use e.g. 
+        <a href="http://marc.theaimsgroup.com/?t=113471292700001&r=1&w=2">http://marc.theaimsgroup.com/?t=113471292700001&amp;r=1&amp;w=2</a> 
+        
+</div>
 </div>
 </div>
-<a name="N10162"></a><a name="Further Reading"></a>
+<a name="N101AF"></a><a name="Further Reading"></a>
 <h2 class="underlined_10">Further Reading</h2>
 <div class="section">
 <p> Congratulations you are now able to work with the structurer. From here 
@@ -796,7 +848,7 @@
     
 </ul>
 </div>
-<a name="N10174"></a><a name="Feedback"></a>
+<a name="N101C1"></a><a name="Feedback"></a>
 <h2 class="underlined_10">Feedback</h2>
 <div class="section">
 <p> Please provide feedback about this document via the <a href="../../mail-lists.html">mailing lists</a>. </p>

Modified: forrest/site/docs_0_80/howto/howto-structurer-dsl.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-structurer-dsl.pdf?rev=358435&r1=358434&r2=358435&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=358435&r1=358434&r2=358435&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Wed Dec 21 17:41:04 2005
@@ -210,9 +210,6 @@
 <a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins in-place if src available</a>
 </li>
 <li>
-<a href="#%5BFOR-748%5D+forrest+war%3A+Cannot+load+%27resource%3A%2F%2Fplugins.xconf+...+WEB-INF%2Fcocoon.xconf">[FOR-748] forrest war: Cannot load 'resource://plugins.xconf ... WEB-INF/cocoon.xconf</a>
-</li>
-<li>
 <a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</a>
 </li>
 <li>
@@ -243,9 +240,6 @@
 <a href="#%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated">[FOR-721] entries without labels in site.xml are now being crawled and generated</a>
 </li>
 <li>
-<a href="#%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest">[FOR-699] Beginner HowTos for installing Forrest</a>
-</li>
-<li>
 <a href="#%5BFOR-644%5D+whitespace+cleanup">[FOR-644] whitespace cleanup</a>
 </li>
 <li>
@@ -260,6 +254,12 @@
 <li>
 <a href="#%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins">[FOR-726] use locationmap in all of the plugins</a>
 </li>
+<li>
+<a href="#%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest">[FOR-699] Beginner HowTos for installing Forrest</a>
+</li>
+<li>
+<a href="#%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer">[FOR-765] forrest war gets NoSuchMethodError for some core transformer</a>
+</li>
 </ul>
 </div>
 <div class="note">
@@ -420,17 +420,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N10081"></a><a name="%5BFOR-748%5D+forrest+war%3A+Cannot+load+%27resource%3A%2F%2Fplugins.xconf+...+WEB-INF%2Fcocoon.xconf"></a>
-<h2 class="underlined_10">[FOR-748] forrest war: Cannot load 'resource://plugins.xconf ... WEB-INF/cocoon.xconf</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-748">http://issues.apache.org/jira/browse/FOR-748</a>
-</p>
-<p>Doing 'forrest war' and copy to a full Jetty/webapps/ and start Jetty, then get this error on Jetty startup ...
-&lt;br&gt;
-Cannot load '&lt;a href="resource://plugins.xconf"&gt;resource://plugins.xconf&lt;/a&gt;' at ... webapp/WEB-INF/cocoon.xconf:31:44</p>
-</div>
-<a name="N1008F"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<a name="N10081"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
 <h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
 <div class="section">
 <p>
@@ -476,7 +466,7 @@
 &lt;br&gt;
 the ampersand in the link href attribute is not.</p>
 </div>
-<a name="N1009D"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<a name="N1008F"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
 <h2 class="underlined_10">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</h2>
 <div class="section">
 <p>
@@ -490,7 +480,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N100AB"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N1009D"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
 <h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext links</h2>
 <div class="section">
 <p>
@@ -498,7 +488,7 @@
 </p>
 <p>In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).</p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<a name="N100AB"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
 <h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected appropriately</h2>
 <div class="section">
 <p>
@@ -520,7 +510,7 @@
 &lt;br&gt;
 &amp;nbsp;&amp;nbsp;Lorenz Froihofer.</p>
 </div>
-<a name="N100C7"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N100B9"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
 <h2 class="underlined_10">[FOR-546] Sitemap reference doc should be updated to reflect plugin architecture</h2>
 <div class="section">
 <p>
@@ -552,7 +542,7 @@
 &lt;br&gt;
 I found out about this because my sitemap uses the fo2pdf too (docbook to PDF), and had to add the serializer.</p>
 </div>
-<a name="N100D5"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<a name="N100C7"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
 <h2 class="underlined_10">[FOR-560] Remove duplicate jars from eclipse plugins</h2>
 <div class="section">
 <p>
@@ -560,7 +550,7 @@
 </p>
 <p>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.</p>
 </div>
-<a name="N100E3"></a><a name="%5BFOR-562%5D+Update+Plugins+howto"></a>
+<a name="N100D5"></a><a name="%5BFOR-562%5D+Update+Plugins+howto"></a>
 <h2 class="underlined_10">[FOR-562] Update Plugins howto</h2>
 <div class="section">
 <p>
@@ -588,7 +578,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N100F1"></a><a name="%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed"></a>
+<a name="N100E3"></a><a name="%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed"></a>
 <h2 class="underlined_10">[FOR-677] leading slash in gathered URIs causes double the number of links to be processed</h2>
 <div class="section">
 <p>
@@ -608,7 +598,7 @@
 &lt;br&gt;
 However, we do have a sitemap transformer to &amp;quot;relativize&amp;quot; and &amp;quot;absolutize&amp;quot; the links. Should it always trim the leading slash? Or are there cases where that should not happen, so cannot generalise?</p>
 </div>
-<a name="N100FF"></a><a name="%5BFOR-705%5D+Target+of+LocationMap+rewriteDemo+causes+build+failure+when+target+not+available"></a>
+<a name="N100F1"></a><a name="%5BFOR-705%5D+Target+of+LocationMap+rewriteDemo+causes+build+failure+when+target+not+available"></a>
 <h2 class="underlined_10">[FOR-705] Target of LocationMap rewriteDemo causes build failure when target not available</h2>
 <div class="section">
 <p>
@@ -636,7 +626,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N1010D"></a><a name="%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated"></a>
+<a name="N100FF"></a><a name="%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated"></a>
 <h2 class="underlined_10">[FOR-721] entries without labels in site.xml are now being crawled and generated</h2>
 <div class="section">
 <p>
@@ -648,15 +638,7 @@
 &lt;br&gt;
 This is most likely a side-effect of the workaround for issue FOR-675</p>
 </div>
-<a name="N1011B"></a><a name="%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest"></a>
-<h2 class="underlined_10">[FOR-699] Beginner HowTos for installing Forrest</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-699">http://issues.apache.org/jira/browse/FOR-699</a>
-</p>
-<p>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.</p>
-</div>
-<a name="N10129"></a><a name="%5BFOR-644%5D+whitespace+cleanup"></a>
+<a name="N1010D"></a><a name="%5BFOR-644%5D+whitespace+cleanup"></a>
 <h2 class="underlined_10">[FOR-644] whitespace cleanup</h2>
 <div class="section">
 <p>
@@ -668,7 +650,7 @@
 &lt;br&gt;
 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.</p>
 </div>
-<a name="N10137"></a><a name="%5BFOR-645%5D+patches+for+whitespace+cleanup"></a>
+<a name="N1011B"></a><a name="%5BFOR-645%5D+patches+for+whitespace+cleanup"></a>
 <h2 class="underlined_10">[FOR-645] patches for whitespace cleanup</h2>
 <div class="section">
 <p>
@@ -676,7 +658,7 @@
 </p>
 <p>Use this issue to provide patches for the whitespace cleanup.</p>
 </div>
-<a name="N10145"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N10129"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
 <h2 class="underlined_10">[FOR-210] whole-site html and pdf: broken link faq, broken image links</h2>
 <div class="section">
 <p>
@@ -686,7 +668,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N10153"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<a name="N10137"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
 <h2 class="underlined_10">[FOR-200] Locationmap for Forrest and Users</h2>
 <div class="section">
 <p>
@@ -698,7 +680,7 @@
 &lt;br&gt;
 Beware that it will not work for raw files that are not linked, as this &amp;quot;feature&amp;quot; currently uses a fixed dir being being copied by Ant.</p>
 </div>
-<a name="N10161"></a><a name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<a name="N10145"></a><a name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
 <h2 class="underlined_10">[FOR-726] use locationmap in all of the plugins</h2>
 <div class="section">
 <p>
@@ -709,6 +691,22 @@
 
 &lt;br&gt;
 (Perhaps we need Jira sub-tasks for each plugin.)</p>
+</div>
+<a name="N10153"></a><a name="%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest"></a>
+<h2 class="underlined_10">[FOR-699] Beginner HowTos for installing Forrest</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-699">http://issues.apache.org/jira/browse/FOR-699</a>
+</p>
+<p>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.</p>
+</div>
+<a name="N10161"></a><a name="%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer"></a>
+<h2 class="underlined_10">[FOR-765] forrest war gets NoSuchMethodError for some core transformer</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-765">http://issues.apache.org/jira/browse/FOR-765</a>
+</p>
+<p>Until recently we could run forrest as a WAR. With today's SVN r356945 it gets past the Cocoon startup phase, then on the first client request it suffers some error which causes a NoSuchMethodError. See attached log ... no other clues. This happens for any site, e.g. 'forrest seed-sample war'. All is okay for 'forrest seed-sample run'.</p>
 </div>
 </div>
 <!--+

Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=358435&r1=358434&r2=358435&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/guidelines.html
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.html?rev=358435&r1=358434&r2=358435&view=diff
==============================================================================
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Wed Dec 21 17:41:04 2005
@@ -952,6 +952,11 @@
 http://marc.theaimsgroup.com/?t=112504310100005
 [Proposal] Development process and a stable trunk
 
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=113521408020541
+when to make a release of a branch
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112643002807899
+How to apply an update to 0.7
+
     </pre>
 </div>
 

Modified: forrest/site/guidelines.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.pdf?rev=358435&r1=358434&r2=358435&view=diff
==============================================================================
Binary files - no diff available.