gmazza      2005/01/03 14:39:27

  Modified:    src/documentation/content/xdocs news.xml relnotes.xml
                        site.xml
               src/documentation/content/xdocs/dev api-doc.xml
  Log:
  Removed URL references to nagoya.
  
  Revision  Changes    Path
  1.24      +3 -3      xml-fop/src/documentation/content/xdocs/news.xml
  
  Index: news.xml
  ===================================================================
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- news.xml  29 Nov 2004 17:30:42 -0000      1.23
  +++ news.xml  3 Jan 2005 22:39:27 -0000       1.24
  @@ -106,7 +106,7 @@
       <section>
         <title>23 December 2002 - Official FOP Wiki</title>
         <p>
  -      See <link 
href="http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages";
  +      See <link href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectPages";
         >FOP project pages</link> at the ApacheWiki.
         </p>
       </section>
  
  
  
  1.14      +3 -3      xml-fop/src/documentation/content/xdocs/relnotes.xml
  
  Index: relnotes.xml
  ===================================================================
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/relnotes.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- relnotes.xml      29 Nov 2004 17:30:42 -0000      1.13
  +++ relnotes.xml      3 Jan 2005 22:39:27 -0000       1.14
  @@ -34,7 +34,7 @@
         no, sk, tr) have been removed due to licensing reasons
         (en_GB hyphenation has been renamed to en).
         We're still working on this issue
  -      (see <link 
href="http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003";>
  +      (see <link 
href="http://wiki.apache.org/xmlgraphics-fop/FOPAudits/March2003";>
         Wiki</link> for details).
       </li>
       <li>Documentation is now built with <link 
href="http://xml.apache.org/forrest/";>
  
  
  
  1.8       +2 -2      xml-fop/src/documentation/content/xdocs/site.xml
  
  Index: site.xml
  ===================================================================
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/site.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- site.xml  29 Nov 2004 17:30:42 -0000      1.7
  +++ site.xml  3 Jan 2005 22:39:27 -0000       1.8
  @@ -53,7 +53,7 @@
       <xsl-fo label="XSL-FO" href="fo.html"/>
       <examples label="Examples" href="examples.html"/>
       <bugs label="Bugs" href="bugs.html"/>
  -    <wiki label="Wiki" 
href="http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages"/>
  +    <wiki label="Wiki" 
href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectPages"/>
       <other label="Other" href="resources.html"/>
     </resources>
   
  @@ -72,7 +72,7 @@
   
       <design label="Design">
         <basics label="Resolved" href="site:design/"/>
  -      <unresolved label="Unresolved (Wiki)" 
href="http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages"/>
  +      <unresolved label="Unresolved (Wiki)" 
href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectPages"/>
         <svg label="SVG" href="svg.html"/>
         <extensions label="Extensions" href="extensions.html"/>
       </design>
  
  
  
  1.7       +5 -5      xml-fop/src/documentation/content/xdocs/dev/api-doc.xml
  
  Index: api-doc.xml
  ===================================================================
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/api-doc.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- api-doc.xml       2 Mar 2004 21:41:12 -0000       1.6
  +++ api-doc.xml       3 Jan 2005 22:39:27 -0000       1.7
  @@ -25,12 +25,12 @@
     <body>
       <section id="gump">
         <title>On-line Access (through Gump)</title>
  -      <p>FOP (and many other Apache projects) use <link 
href="http://jakarta.apache.org/gump";>Apache Gump</link> to do a test build 
several times each day. One of the useful byproducts of this process is that 
javadocs can be created and made available.</p>
  +      <p>FOP (and many other Apache projects) use <link 
href="http://gump.apache.org/";>Apache Gump</link> to do a test build several 
times each day. One of the useful byproducts of this process is that javadocs 
can be created and made available.</p>
         <p>First, determine which line of development code you wish to see. If 
you don't know, you probably want the "Maintenance Branch", which is the line 
that currently produces FOP releases. See <link 
href="index.html#lines">Development Lines</link> for more details.</p>
         <warning>Javadocs for both development lines are made from current CVS 
code, and are not tied to any particular release. Both the documentation and 
the API may be different, even if you are working with the correct branch. 
Currently, the only way to obtain API documentation for a specific release is 
to <link href="#self-built">build it yourself</link>.</warning>
         <ul>
  -        <li><link 
href="http://nagoya.apache.org/gump/javadoc/xml-fop-maintenance/build/javadocs/index.html";>Javadocs
 for Maintenance Branch</link></li>
  -        <li><link 
href="http://nagoya.apache.org/gump/javadoc/xml-fop/build/javadocs/index.html";>Javadocs
 for Trunk (Redesign)</link></li>
  +        <li><link 
href="http://gump.apache.org/javadoc/xml-fop-maintenance/build/javadocs/index.html";>Javadocs
 for Maintenance Branch</link></li>
  +        <li><link 
href="http://gump.apache.org/javadoc/xml-fop/build/javadocs/index.html";>Javadocs
 for Trunk (Redesign)</link></li>
         </ul>
         <note>If the links return an "Object not found!" message or otherwise 
do not work properly, it is probably because of a build error. Please raise a 
question on the <link href="../maillist.html#fop-user">fop-user mailing 
list</link> so that any problems can be fixed before the next build.</note>
       </section>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to