db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From myrn...@apache.org
Subject svn commit: r1450510 - /db/derby/site/trunk/src/documentation/content/xdocs/papers/derby_web.xml
Date Tue, 26 Feb 2013 22:56:04 GMT
Author: myrnavl
Date: Tue Feb 26 22:56:04 2013
New Revision: 1450510

URL: http://svn.apache.org/r1450510
Log:
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:
    db/derby/site/trunk/src/documentation/content/xdocs/papers/derby_web.xml

Modified: db/derby/site/trunk/src/documentation/content/xdocs/papers/derby_web.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/papers/derby_web.xml?rev=1450510&r1=1450509&r2=1450510&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/papers/derby_web.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/papers/derby_web.xml Tue Feb 26 22:56:04
2013
@@ -170,16 +170,16 @@ testing them outside the Derby web site 
 <title>Create a Forrest seed site</title>
 <p>
 The
-<em><a href="http://forrest.apache.org/docs_0_70/your-project.html">Using Forrest:
+<em><a href="http://forrest.apache.org/docs_0_80/your-project.html">Using Forrest:
 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:
 </p>
 
 <ul>
-   <li> <a href="http://forrest.apache.org/mirrors.cgi">Download</a>
+   <li> <a href="http://archive.apache.org/dist/forrest/0.8/">Download</a>
         Forrest 0.8. </li>
-   <li> <a href="http://forrest.apache.org/docs_0_70/your-project.html#installing">Install
Forrest and set up your environment</a>.  </li>
+   <li> <a 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, <code>cd</code> into it,
         and enter '<code>forrest seed</code>' to initialize a new project.
    </li>
@@ -286,7 +286,7 @@ which are both quite excellent:
 	
 <ul>	
  	<li><a href="http://www.jedit.org">jEdit</a> (GPL) with the jEdit XML
plugin.
-<a href="http://forrest.apache.org/docs_0_70/catalog.html#jedit">See the 
+<a href="http://forrest.apache.org/docs_0_80/catalog.html#jedit">See the 
 Forrest jEdit configuration instructions</a>.</li>
 	<li><a href="http://xmlbuddy.com">XMLBuddy eclipse plugin</a> (free).
Caches
 	the DTD, but am looking for a way to resolve locally. 
@@ -329,7 +329,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 href="http://forrest.apache.org/docs_0_70/catalog.html">Forrest web site</a>.
+<a href="http://forrest.apache.org/docs_0_80/catalog.html">Forrest web site</a>.
 </p>
 
 </section>
@@ -670,13 +670,14 @@ of files to your ~/.subversion/config fi
 
 <p>
 When you're ready to commit,
-one way is to enter the command shown below
-one level above the <code>src</code> and
-<code>build</code> directories:
+you have to separately commit the changes to the <code>src</code> and <code>build/site</code>
directories:
 </p>
 
 <source>
-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" 
 </source>
 </section>
 
@@ -684,7 +685,7 @@ svn commit --message "here is my commit 
 <title>9. Make web site changes visible</title>
 
 <p>
-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:
 </p>
 
 <source>
@@ -694,8 +695,10 @@ svn update
 </source>
 
 <p>
-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 <code>build/site</code> tree will get synced right away, 
+so there is no need for this.
 </p>
 
 </section>



Mime
View raw message