db-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From myrn...@apache.org
Subject svn commit: r852131 - /websites/production/db/content/derby/papers/derby_web.html
Date Tue, 26 Feb 2013 22:56:36 GMT
Author: myrnavl
Date: Tue Feb 26 22:56:36 2013
New Revision: 852131

DERBY-6077; web site needs updatin on a few points
  - correcting links broken by rearranging of Apache Forrest's web site since their release
of 0.9
  - correcting the instruction of how to commit changes, which needs to be in two steps now.


Modified: websites/production/db/content/derby/papers/derby_web.html
--- websites/production/db/content/derby/papers/derby_web.html (original)
+++ websites/production/db/content/derby/papers/derby_web.html Tue Feb 26 22:56:36 2013
@@ -405,7 +405,7 @@ testing them outside the Derby web site 
 <h3 class="boxed">Create a Forrest seed site</h3>
-<em><a class="external" href="http://forrest.apache.org/docs_0_70/your-project.html">Using
+<em><a class="external" href="http://forrest.apache.org/docs_0_80/your-project.html">Using
 A tutorial on how to use Forrest in your own projects</a></em> guide 
 provides an excellent overview of Forrest.
 Below are some simple steps to get started:
@@ -413,11 +413,11 @@ Below are some simple steps to get start
-<a class="external" href="http://forrest.apache.org/mirrors.cgi">Download</a>
+<a class="external" href="http://archive.apache.org/dist/forrest/0.8/">Download</a>
         Forrest 0.8. </li>
-<a class="external" href="http://forrest.apache.org/docs_0_70/your-project.html#installing">Install
Forrest and set up your environment</a>.  </li>
+<a class="external" href="http://forrest.apache.org/docs_0_80/your-project.html#installing">Install
Forrest and set up your environment</a>.  </li>
 <li> Create a new directory, <span class="codefrag">cd</span> into it,
         and enter '<span class="codefrag">forrest seed</span>' to initialize
a new project.
@@ -537,7 +537,7 @@ which are both quite excellent:
 <a class="external" href="http://www.jedit.org">jEdit</a> (GPL) with the jEdit
XML plugin.
-<a class="external" href="http://forrest.apache.org/docs_0_70/catalog.html#jedit">See
+<a class="external" href="http://forrest.apache.org/docs_0_80/catalog.html#jedit">See
 Forrest jEdit configuration instructions</a>.</li>
@@ -576,7 +576,7 @@ However,
 if you use a tool to edit Forrest XML files that validates the XML, 
 then you should configure that tool to use a catalog entity resolver per 
 the instructions on the 
-<a class="external" href="http://forrest.apache.org/docs_0_70/catalog.html">Forrest
web site</a>.
+<a class="external" href="http://forrest.apache.org/docs_0_80/catalog.html">Forrest
web site</a>.
 When you're satisfied with how your new page looks on your seed site,
@@ -902,17 +902,18 @@ of files to your ~/.subversion/config fi
 When you're ready to commit,
-one way is to enter the command shown below
-one level above the <span class="codefrag">src</span> and
-<span class="codefrag">build</span> directories:
+you have to separately commit the changes to the <span class="codefrag">src</span>
and <span class="codefrag">build/site</span> directories:
 <pre class="code">
-svn commit --message "here is my commit message" src build/site 
+cd src
+svn commit --message "here is my commit message" 
+cd ../build/site 
+svn commit --message "here is my commit message" 
 <a name="N103E0"></a><a name="9.+Make+web+site+changes+visible"></a>
 <h3 class="boxed">9. Make web site changes visible</h3>
-A Derby committer can make web site changes visible as follows:
+A Derby committer can force the source tree to be updated to the latest change as follows:
 <pre class="code">
 ssh -l <em>your_apache_login</em> people.apache.org
@@ -920,10 +921,12 @@ cd /www/db.apache.org/derby
 svn update
-www.apache.org automatically syncs up with people.apache.org every couple hours
-(the specific schedule could change).
+However, www.apache.org automatically syncs up with people.apache.org every couple hours
+(the specific schedule could change)
+and the <span class="codefrag">build/site</span> tree will get synced right away,

+so there is no need for this.
-<a name="N103F4"></a><a name="10.+Considering+a+quick+fix+to+the+build+tree%3F"></a>
+<a name="N103F7"></a><a name="10.+Considering+a+quick+fix+to+the+build+tree%3F"></a>
 <h3 class="boxed">10. Considering a quick fix to the build tree?</h3>
 If you modify a file in the <span class="codefrag">build/site</span> tree, 

View raw message