db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From se...@apache.org
Subject cvs commit: jakarta-turbine-torque/xdocs jar-guide.xml
Date Mon, 27 Jan 2003 11:49:26 GMT
seade       2003/01/27 03:49:25

  Modified:    xdocs    jar-guide.xml
  Log:
  Fixed bad link.
  
  Revision  Changes    Path
  1.4       +1 -1      jakarta-turbine-torque/xdocs/jar-guide.xml
  
  Index: jar-guide.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-torque/xdocs/jar-guide.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- jar-guide.xml	28 Sep 2002 01:24:43 -0000	1.3
  +++ jar-guide.xml	27 Jan 2003 11:49:25 -0000	1.4
  @@ -13,7 +13,7 @@
   
   <p>
     The standard practice for using Torque has been to download the jar, unjar it
  -  to get the directory structure given in the <a href="user-guide.xml">user
  +  to get the directory structure given in the <a href="user-guide.html">user
     guide</a>, and  somehow either integrate your source tree and Torque's 
     un-jared directory  structure. While doable, this was less than desirable, 
     especially when working with prespecified directory structures, such as that
  
  
  

Mime
View raw message