db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kmars...@apache.org
Subject svn commit: r799768 [1/2] - in /db/derby/site/trunk: build/site/ build/site/manuals/ build/site/papers/DerbyTut/ build/site/releases/ src/documentation/conf/ src/documentation/content/xdocs/ src/documentation/content/xdocs/papers/DerbyTut/ src/document...
Date Fri, 31 Jul 2009 23:04:15 GMT
Author: kmarsden
Date: Fri Jul 31 23:04:15 2009
New Revision: 799768

URL: http://svn.apache.org/viewvc?rev=799768&view=rev
Log:
DERBY-4308 - Conduct release tasks for 10.5.2 release
Update web site for 10.5.2.0 release


Added:
    db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi   (with props)
    db/derby/site/trunk/build/site/releases/release-10.5.2.0.html
    db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.5.2.0.cgi   (with props)
    db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.5.2.0.html   (with props)
Removed:
    db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.5.1.1.cgi
Modified:
    db/derby/site/trunk/build/site/derby_downloads.html
    db/derby/site/trunk/build/site/manuals/index.html
    db/derby/site/trunk/build/site/papers/DerbyTut/install_software.html
    db/derby/site/trunk/build/site/releases/release-10.5.1.1.html
    db/derby/site/trunk/src/documentation/conf/cli.xconf
    db/derby/site/trunk/src/documentation/content/xdocs/derby_downloads.xml
    db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/install_software.xml
    db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.5.1.1.html

Modified: db/derby/site/trunk/build/site/derby_downloads.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/derby_downloads.html?rev=799768&r1=799767&r2=799768&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/derby_downloads.html (original)
+++ db/derby/site/trunk/build/site/derby_downloads.html Fri Jul 31 23:04:15 2009
@@ -157,14 +157,15 @@
 </div>
 
 
+
 <a name="N1000D"></a><a name="Latest+Official+Release"></a>
 <h2 class="boxed"> Latest Official Release </h2>
 <div class="section">
 <ul>
    
 <li> 
-<a href="releases/release-10.5.1.1.cgi">10.5.1.1</a> 
-   (April 28, 2009 / SVN 764942)
+<a href="releases/release-10.5.2.0.cgi">10.5.2.0</a> 
+   (July 30, 2009 / SVN 794445)
    </li>
    
 <li> 
@@ -186,6 +187,11 @@
 <ul>
    
 <li> 
+<a href="releases/release-10.5.1.1.html">10.5.1.1</a> 
+   (April 28, 2009 / SVN 764942)
+   </li>
+   
+<li> 
 <a href="releases/release-10.4.1.3.html">10.4.1.3</a> 
    (April 24, 2008 / SVN 648739)
    </li>
@@ -219,7 +225,7 @@
 </div>
 
 
-<a name="N10060"></a><a name="Deprecated+Releases"></a>
+<a name="N10067"></a><a name="Deprecated+Releases"></a>
 <h2 class="boxed">Deprecated Releases</h2>
 <div class="section">
 <p>
@@ -241,7 +247,7 @@
 </div>
 
 
-<a name="N10079"></a><a name="Change+History"></a>
+<a name="N10080"></a><a name="Change+History"></a>
 <h2 class="boxed">Change History</h2>
 <div class="section">
 <p>

Modified: db/derby/site/trunk/build/site/manuals/index.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/manuals/index.html?rev=799768&r1=799767&r2=799768&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/manuals/index.html (original)
+++ db/derby/site/trunk/build/site/manuals/index.html Fri Jul 31 23:04:15 2009
@@ -403,9 +403,9 @@
      
 <tr>
         
-<td colspan="1" rowspan="1"><em>初めての Apache Derby</em></td>
-        <td colspan="1" rowspan="1"> [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html">HTML:書籍の体裁</a>]
-             [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/getstart/">HTML:サイトの体裁</a>]
+<td colspan="1" rowspan="1"><em>���� Apache Derby</em></td>
+        <td colspan="1" rowspan="1"> [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html">HTML:書ç±?ã?®ä½“è£?</a>]
+             [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/getstart/">HTML:サイトã?®ä½“è£?</a>]
         </td>
      
 </tr>
@@ -413,8 +413,8 @@
 <tr>
         
 <td colspan="1" rowspan="1"><em>Derby リファレンスマニュアル</em></td>
-        <td colspan="1" rowspan="1"> [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/ref/ref-single.html">HTML:書籍の体裁</a>]
-             [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/ref/">HTML:サイトの体裁</a>]
+        <td colspan="1" rowspan="1"> [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/ref/ref-single.html">HTML:書ç±?ã?®ä½“è£?</a>]
+             [<a target="_blank" class="fork" href="http://db.apache.org/derby/docs/dev/ja_JP/ref/">HTML:サイトã?®ä½“è£?</a>]
         </td>
      
 </tr>

Modified: db/derby/site/trunk/build/site/papers/DerbyTut/install_software.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/papers/DerbyTut/install_software.html?rev=799768&r1=799767&r2=799768&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/papers/DerbyTut/install_software.html (original)
+++ db/derby/site/trunk/build/site/papers/DerbyTut/install_software.html Fri Jul 31 23:04:15 2009
@@ -465,7 +465,7 @@
 <p>
 Download the binary Apache Derby distribution from the Derby web site at 
 <a href="http://db.apache.org/derby/derby_downloads.html">http://db.apache.org/derby/derby_downloads.html</a>.
-These tutorial instructions use version 10.5.1.1 and 
+These tutorial instructions use version 10.5.2.0 and 
 assume you downloaded one of the binary distribution files 
 listed in the table below:
 </p>
@@ -476,17 +476,17 @@
 </tr>
      
 <tr>
-<td colspan="1" rowspan="1">Windows</td><td colspan="1" rowspan="1">db-derby-10.5.1.1-bin.zip</td>
+<td colspan="1" rowspan="1">Windows</td><td colspan="1" rowspan="1">db-derby-10.5.2.0-bin.zip</td>
 </tr>
      
 <tr>
-<td colspan="1" rowspan="1">UNIX, Linux, and Mac</td><td colspan="1" rowspan="1">db-derby-10.5.1.1-bin.tar.gz</td>
+<td colspan="1" rowspan="1">UNIX, Linux, and Mac</td><td colspan="1" rowspan="1">db-derby-10.5.2.0-bin.tar.gz</td>
 </tr>
 
 </table>
 <p>If a more recent release is available, download that,
    then substitute that version number 
-for <span class="codefrag">10.5.1.1</span> in the following instructions.
+for <span class="codefrag">10.5.2.0</span> in the following instructions.
    </p>
 <a name="N100D0"></a><a name="derby_install"></a>
 <h3 class="boxed">Install Derby</h3>
@@ -500,18 +500,18 @@
     </p>
 <p class="code-block">Windows (use your extraction tool e.g. WinZip -- these instructions use mks unzip):
 mkdir C:\Apache
-copy db-derby-10.5.1.1-bin.zip C:\Apache
+copy db-derby-10.5.2.0-bin.zip C:\Apache
 cd C:\Apache
-unzip db-derby-10.5.1.1-bin.zip
+unzip db-derby-10.5.2.0-bin.zip
 </p>
 <p class="code-block">UNIX:
 mkdir /opt/Apache
-cp db-derby-10.5.1.1-bin.tar.gz /opt/Apache
+cp db-derby-10.5.2.0-bin.tar.gz /opt/Apache
 cd /opt/Apache
-tar xzvf db-derby-10.5.1.1-bin.tar.gz
+tar xzvf db-derby-10.5.2.0-bin.tar.gz
 </p>
 <p>In both cases, the software will now be extracted into a subdirectory
-    named <span class="codefrag">db-derby-10.5.1.1-bin</span>. 
+    named <span class="codefrag">db-derby-10.5.2.0-bin</span>. 
    </p>
 <a name="N100EE"></a><a name="set_derby_install"></a>
 <h3 class="boxed">Set DERBY_INSTALL</h3>
@@ -522,10 +522,10 @@
 your system:
 </p>
 <p class="code-block">Windows:
-C:\&gt; set DERBY_INSTALL=C:\Apache\db-derby-10.5.1.1-bin
+C:\&gt; set DERBY_INSTALL=C:\Apache\db-derby-10.5.2.0-bin
 </p>
 <p class="code-block">UNIX Korn Shell:
-$ export DERBY_INSTALL=/opt/Apache/db-derby-10.5.1.1-bin
+$ export DERBY_INSTALL=/opt/Apache/db-derby-10.5.2.0-bin
 </p>
 <a name="N10103"></a><a name="derby_configure"></a>
 <h3 class="boxed">Configure Embedded Derby</h3>
@@ -581,7 +581,7 @@
    </p>
 <p class="code-block">Windows:
 C:\&gt; cd %DERBY_INSTALL%\bin
-C:\Apache\db-derby-10.5.1.1-bin\bin&gt; setEmbeddedCP.bat
+C:\Apache\db-derby-10.5.2.0-bin\bin&gt; setEmbeddedCP.bat
 </p>
 <p class="code-block">UNIX:
 $ cd $DERBY_INSTALL/bin
@@ -604,13 +604,13 @@
 OS version:      5.1
 Java user name:  user
 Java user home:  C:\Documents and Settings\user
-Java user dir:   C:\Apache\db-derby-10.5.1.1-bin\bin
+Java user dir:   C:\Apache\db-derby-10.5.2.0-bin\bin
 java.specification.name: Java Platform API Specification
 java.specification.version: 1.5
 --------- Derby Information --------
 JRE - JDBC: J2SE 5.0 - JDBC 3.0
-[C:\Apache\db-derby-10.5.1.1-bin\lib\derby.jar] 10.5.1.1 - (764942)
-[C:\Apache\db-derby-10.5.1.1-bin\lib\derbytools.jar] 10.5.1.1 - (764942)
+[C:\Apache\db-derby-10.5.2.0-bin\lib\derby.jar] 10.5.2.0 - (794445)
+[C:\Apache\db-derby-10.5.2.0-bin\lib\derbytools.jar] 10.5.2.0 - (794445)
 ------------------------------------------------------
 ----------------- Locale Information -----------------
 Current Locale :  [English/United States [en_US]]
@@ -619,7 +619,7 @@
 .
 .
 Found support for locale: [zh_TW]
-         version: 10.5.1.1 - (764942)
+         version: 10.5.2.0 - (794445)
 ------------------------------------------------------
 </p>
 <p>
@@ -645,7 +645,7 @@
 </p>
 <p class="code-block">UNIX:
 $ echo $CLASSPATH
-/opt/Apache/db-derby-10.5.1.1-bin/lib/derby.jar:/opt/Apache/db-derby-10.5.1.1-bin/lib/derbytools.jar:
+/opt/Apache/db-derby-10.5.2.0-bin/lib/derby.jar:/opt/Apache/db-derby-10.5.2.0-bin/lib/derbytools.jar:
 </p>
 <p>
 If <span class="codefrag">sysinfo</span> outputs valid information, you're

Modified: db/derby/site/trunk/build/site/releases/release-10.5.1.1.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.5.1.1.html?rev=799768&r1=799767&r2=799768&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/releases/release-10.5.1.1.html (original)
+++ db/derby/site/trunk/build/site/releases/release-10.5.1.1.html Fri Jul 31 23:04:15 2009
@@ -17,36 +17,36 @@
 <body onload="init()">
 <script type="text/javascript">ndeSetTextSize();</script>
 <div id="top">
-<!--+
-    |breadtrail
+<!--+
+    |breadtrail
     +-->
 <div class="breadtrail">
 <a href="http://www.apache.org/">apache</a> &gt; <a href="http://db.apache.org/">db</a><script src="../skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
 </div>
-<!--+
-    |header
+<!--+
+    |header
     +-->
 <div class="header">
-<!--+
-    |start group logo
+<!--+
+    |start group logo
     +-->
 <div class="grouplogo">
 <a href="http://db.apache.org/derby"><img class="logoImage" alt="Apache Derby" src="../images/derby-logo-web.png" title="Derby is a zero-admin Java RDBMS"></a>
 </div>
-<!--+
-    |end group logo
+<!--+
+    |end group logo
     +-->
-<!--+
-    |start Project Logo
+<!--+
+    |start Project Logo
     +-->
 <div class="projectlogoA1">
 <a href="http://db.apache.org"><img class="logoImage" alt="Apache DB Project" src="../images/db-logo-white.png" title="Apache DB creates and maintains database solutions."></a>
 </div>
-<!--+
-    |end Project Logo
+<!--+
+    |end Project Logo
     +-->
-<!--+
-    |start Tabs
+<!--+
+    |start Tabs
     +-->
 <ul id="tabs">
 <li>
@@ -68,36 +68,36 @@
 <a class="unselected" href="../integrate/index.html">Resources</a>
 </li>
 </ul>
-<!--+
-    |end Tabs
+<!--+
+    |end Tabs
     +-->
 </div>
 </div>
 <div id="main">
 <div id="publishedStrip">
-<!--+
-    |start Subtabs
+<!--+
+    |start Subtabs
     +-->
 <div id="level2tabs"></div>
-<!--+
-    |end Endtabs
+<!--+
+    |end Endtabs
     +-->
 <script type="text/javascript"><!--
 document.write("Last Published: " + document.lastModified);
 //  --></script>
 </div>
-<!--+
-    |breadtrail
+<!--+
+    |breadtrail
     +-->
 <div class="breadtrail">
 
              &nbsp;
            </div>
-<!--+
-    |start Menu, mainarea
+<!--+
+    |start Menu, mainarea
     +-->
-<!--+
-    |start Menu
+<!--+
+    |start Menu
     +-->
 <div id="menu">
 <div onclick="SwitchMenu('menu_1.1', '../skin/')" id="menu_1.1Title" class="menutitle">Home</div>
@@ -358,8 +358,8 @@
 </div>
 </div>
 </div>
-<!--+
-    |start Search
+<!--+
+    |start Search
     +-->
 <div class="searchbox">
 <hr>
@@ -368,22 +368,22 @@
                   <input name="Search" value="Search" type="submit">
 </form>
 </div>
-<!--+
-    |end search
+<!--+
+    |end search
     +-->
 <div id="credit"></div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
-<!--+
-  |alternative credits
+<!--+
+  |alternative credits
   +-->
 <div id="credit2"></div>
 </div>
-<!--+
-    |end Menu
+<!--+
+    |end Menu
     +-->
-<!--+
-    |start content
+<!--+
+    |start content
     +-->
 <div id="content">
 <div class="trail">Font size: 
@@ -472,17 +472,7 @@
 <a name="N10010"></a><a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
-<p>Use the links below to download a distribution of Apache Derby from one of our mirrors. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
-<p>You are currently using <strong>[preferred]</strong>. If you encounter a problem with this mirror, then please select another. If all mirrors are failing, there are backup mirrors at the end of the list. See <a class="external" href="http://www.apache.org/mirrors/">status</a> of mirrors.</p>
-<a name="SelectMirror"></a>
-<form action="[location]" method="get" id="SelectMirror">Other mirrors: <select name="Preferred">
-<!--[if-any http] [for http]--><option value="[http]">[http]</option>
-<!--[end] [end]-->
-<!--[if-any ftp] [for ftp]--><option value="[ftp]">[ftp]</option>
-<!--[end] [end]-->
-<!--[if-any backup] [for backup]--><option value="[backup]">[backup] (backup)</option>
-<!--[end] [end]--></select> <input type="submit" value="Change">
-</form>
+<p>Use the links below to download a distribution of Apache Derby. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
 <p>There are four different distributions:</p>
 <ul>
 <li>bin distribution - contains the documentation, javadoc, and jar files for Derby.</li>
@@ -491,32 +481,32 @@
 <li>src distribution - contains the Derby source tree at the point which the binaries were built.</li>
 </ul>
 <p>
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.zip">db-derby-10.5.1.1-bin.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.zip.md5">MD5</a>]<br> 
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.tar.gz">db-derby-10.5.1.1-bin.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.tar.gz.md5">MD5</a>]</p>
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.zip">db-derby-10.5.1.1-bin.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.zip.md5">MD5</a>]<br> 
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.tar.gz">db-derby-10.5.1.1-bin.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-bin.tar.gz.md5">MD5</a>]</p>
 <p>
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.zip">db-derby-10.5.1.1-lib.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.zip.md5">MD5</a>]<br> 
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.tar.gz">db-derby-10.5.1.1-lib.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.tar.gz.md5">MD5</a>]</p>
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.zip">db-derby-10.5.1.1-lib.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.zip.md5">MD5</a>]<br> 
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.tar.gz">db-derby-10.5.1.1-lib.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib.tar.gz.md5">MD5</a>]</p>
 <p>
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.zip">db-derby-10.5.1.1-lib-debug.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.zip.md5">MD5</a>]<br> 
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.tar.gz">db-derby-10.5.1.1-lib-debug.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.tar.gz.md5">MD5</a>]</p>
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.zip">db-derby-10.5.1.1-lib-debug.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.zip.md5">MD5</a>]<br> 
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.tar.gz">db-derby-10.5.1.1-lib-debug.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-lib-debug.tar.gz.md5">MD5</a>]</p>
 <p>
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.zip">db-derby-10.5.1.1-src.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.zip.md5">MD5</a>]<br> 
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.tar.gz">db-derby-10.5.1.1-src.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.tar.gz.md5">MD5</a>] (Note that, due to long filenames, you will need gnu tar to unravel this tarball.)</p>
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.zip">db-derby-10.5.1.1-src.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.zip.md5">MD5</a>]<br> 
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.tar.gz">db-derby-10.5.1.1-src.tar.gz</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.tar.gz.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/db-derby-10.5.1.1-src.tar.gz.md5">MD5</a>] (Note that, due to long filenames, you will need gnu tar to unravel this tarball.)</p>
 <p>There are two separate Eclipse plugins for Derby:</p>
 <ul>
 <li>derby_core_plugin - provides the Derby jar files to other plugins in Eclipse.</li>
 <li>derby_ui_plugin - provides an Apache Derby Nature in Eclipse for easy database application development.</li>
 </ul>
 <p>
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/derby_core_plugin_10.5.1.764942.zip">derby_core_plugin_10.5.1.764942.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_core_plugin_10.5.1.764942.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_core_plugin_10.5.1.764942.zip.md5">MD5</a>]<br> 
-<a href="[preferred]/db/derby/db-derby-10.5.1.1/derby_ui_doc_plugin_1.1.2.zip">derby_ui_doc_plugin_1.1.2.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_ui_doc_plugin_1.1.2.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_ui_doc_plugin_1.1.2.zip.md5">MD5</a>]</p>
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_core_plugin_10.5.1.764942.zip">derby_core_plugin_10.5.1.764942.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_core_plugin_10.5.1.764942.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_core_plugin_10.5.1.764942.zip.md5">MD5</a>]<br> 
+<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_ui_doc_plugin_1.1.2.zip">derby_ui_doc_plugin_1.1.2.zip</a> [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_ui_doc_plugin_1.1.2.zip.asc">PGP</a>] [<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.5.1.1/derby_ui_doc_plugin_1.1.2.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using the 10 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N100DF"></a><a name="Release Notes for Derby 10.5.1.1"></a>
+<a name="N100BC"></a><a name="Release Notes for Derby 10.5.1.1"></a>
 <h2 class="boxed">Release Notes for Derby 10.5.1.1</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.5.1.1 and the preceding release 10.4.2.0.</p>
-<a name="N100E7"></a><a name="Overview"></a>
+<a name="N100C4"></a><a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs.</p>
 <p>Derby functionality includes:</p>
@@ -526,7 +516,7 @@
 <li>Network client JDBC drivers</li>
 <li>Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)</li>
 </ul>
-<a name="N100FA"></a><a name="New+Features"></a>
+<a name="N100D7"></a><a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <p>This is a feature release. The following features were added.</p>
 <ul>
@@ -547,7 +537,7 @@
 <li>
 <strong>SYSCS_UTIL.SYSCS_UPDATE_STATISTICS</strong> - New system procedure that updates cardinality statistics (or creates them if they do not exist) for a table's index or for all the indexes on a table, allowing a user to ensure that a query plan based on the most recent state of the table can be created.</li>
 </ul>
-<a name="N10127"></a><a name="Bug+Fixes"></a>
+<a name="N10104"></a><a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <p>The following issues are addressed by Derby release 10.5.1.1. These issues are not addressed in the preceding 10.4.2.0 release.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4" border="2">
@@ -1659,7 +1649,7 @@
 <td><a class="external" href="http://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a></td><td>A connection request that has a default schema that is being created by another transaction will fail to connect</td>
 </tr>
 </table>
-<a name="N10B48"></a><a name="Issues"></a>
+<a name="N10B25"></a><a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <p>Compared with the previous release (10.4.2.0), Derby release 10.5.1.1 introduces the following incompatibilities. These merit your special attention.</p>
 <ul>
@@ -1725,55 +1715,55 @@
 </li>
 </ul>
 <hr>
-<a name="N10BA9"></a><a name="Note+for+DERBY-4073"></a>
+<a name="N10B86"></a><a name="Note+for+DERBY-4073"></a>
 <h4>Note for DERBY-4073</h4>
-<a name="N10BAF"></a><a name="Summary+of+Change"></a>
+<a name="N10B8C"></a><a name="Summary+of+Change"></a>
 <h5>Summary of Change</h5>
 <p>The method <tt>setSsl(int)</tt> has been removed from the client data source classes.</p>
-<a name="N10BB8"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
+<a name="N10B95"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>The application will either fail to compile, or experience a <tt>NoSuchMethodError</tt>. Only applications invoking the removed method are affected.</p>
-<a name="N10BC1"></a><a name="Incompatibilities+with+Previous+Release"></a>
+<a name="N10B9E"></a><a name="Incompatibilities+with+Previous+Release"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>The method <tt>setSsl(int)</tt> can no longer be used to configure SSL with the client data sources.</p>
-<a name="N10BCA"></a><a name="Rationale+for+Change"></a>
+<a name="N10BA7"></a><a name="Rationale+for+Change"></a>
 <h5>Rationale for Change</h5>
 <p>Having two <tt>setSsl</tt>-methods caused choice problems for some applications using Derby data sources and also configuring the data source through introspection, since there were two methods called setSsl; <tt>setSsl(int)</tt> and <tt>setSsl(String)</tt>.</p>
-<a name="N10BD9"></a><a name="Application+Changes+Required"></a>
+<a name="N10BB6"></a><a name="Application+Changes+Required"></a>
 <h5>Application Changes Required</h5>
 <p>Use <tt>setSsl(String)</tt> instead of <tt>setSsl(int)</tt>.</p>
 <hr>
-<a name="N10BE6"></a><a name="Note+for+DERBY-4050"></a>
+<a name="N10BC3"></a><a name="Note+for+DERBY-4050"></a>
 <h4>Note for DERBY-4050</h4>
-<a name="N10BEC"></a><a name="Summary+of+Change-N10BEC"></a>
+<a name="N10BC9"></a><a name="Summary+of+Change-N10BC9"></a>
 <h5>Summary of Change</h5>
 <p>Table growth may result from multi-threaded Clob updates before the fix for DERBY-4050.</p>
-<a name="N10BF2"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10BF2"></a>
+<a name="N10BCF"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10BCF"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Before the fix for DERBY-4050, applications may have seen growth in the size of the database, particularly the size of the dat files for Clob tables, when doing updates to the Clob tables from multiple threads. The fix for DERBY-4050 will prevent future growth but will not reclaim space consumed by the bug in the past. To reclaim the space, a full offline compress of the clob table is needed. See the Derby documentation for usage of <a href="http://db.apache.org/derby/docs/10.4/ref/rrefaltertablecompress.html">SYSCS_UTIL.SYSCS_COMPRESS_TABLE</a>
 </p>
-<a name="N10BFB"></a><a name="Incompatibilities+with+Previous+Release-N10BFB"></a>
+<a name="N10BD8"></a><a name="Incompatibilities+with+Previous+Release-N10BD8"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>none</p>
-<a name="N10C01"></a><a name="Rationale+for+Change-N10C01"></a>
+<a name="N10BDE"></a><a name="Rationale+for+Change-N10BDE"></a>
 <h5>Rationale for Change</h5>
 <p>DERBY-4050 fixes a bug in space reclamation.</p>
-<a name="N10C07"></a><a name="Application+Changes+Required-N10C07"></a>
+<a name="N10BE4"></a><a name="Application+Changes+Required-N10BE4"></a>
 <h5>Application Changes Required</h5>
 <p>The compress table should only need to be run once if the fix for DERBY-4050 has been applied. No application changes should be required.</p>
 <hr>
-<a name="N10C0E"></a><a name="Note+for+DERBY-4042"></a>
+<a name="N10BEB"></a><a name="Note+for+DERBY-4042"></a>
 <h4>Note for DERBY-4042</h4>
-<a name="N10C14"></a><a name="Summary+of+Change-N10C14"></a>
+<a name="N10BF1"></a><a name="Summary+of+Change-N10BF1"></a>
 <h5>Summary of Change</h5>
 <p>Format of file name arguments to the import procedures changed for files with single quotes (') in their names.</p>
-<a name="N10C1A"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10C1A"></a>
+<a name="N10BF7"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10BF7"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, applications that imported data from a file whose file name contained a single quote (') character would fail unless they replaced each single quote in the file name argument to the import procedure with two single quotes. Now this has changed and Derby does not understand the file name argument unless it has the same number of single quote characters as the actual file name. Applications that worked around the problems in earlier releases by adding extra single quotes, will now see exceptions like the following:</p>
 <pre>ERROR XIE04: Data file not found: Rock''n''roll.csv
 </pre>
 <p>Applications that do not import files whose names contain single quotes will not be affected by this change.</p>
-<a name="N10C24"></a><a name="Incompatibilities+with+Previous+Release-N10C24"></a>
+<a name="N10C01"></a><a name="Incompatibilities+with+Previous+Release-N10C01"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Previous releases required file name arguments to the import procedures to double each occurrence of a single quote in the file name, like this when importing a file called <tt>C:/Chip's/TERMS.dat</tt>:</p>
 <pre>PreparedStatement ps = conn.prepareStatement(
@@ -1790,19 +1780,19 @@
 ps.setString(1, "C:/Chip's/TERMS.dat");
 ps.execute();
 </pre>
-<a name="N10C37"></a><a name="Rationale+for+Change-N10C37"></a>
+<a name="N10C14"></a><a name="Rationale+for+Change-N10C14"></a>
 <h5>Rationale for Change</h5>
 <p>It is more intuitive if the file name arguments match the actual file names. Also, in the previous releases there were some combinations of single quotes and other special characters (like double quotes) that it was not possible to get to work even with the workaround.</p>
-<a name="N10C3D"></a><a name="Application+Changes+Required-N10C3D"></a>
+<a name="N10C1A"></a><a name="Application+Changes+Required-N10C1A"></a>
 <h5>Application Changes Required</h5>
 <p>Applications that work around the issue in previous releases by adding extra single quotes to the file name arguments, must be changed so that they do not add extra single quote characters.</p>
 <hr>
-<a name="N10C44"></a><a name="Note+for+DERBY-4008"></a>
+<a name="N10C21"></a><a name="Note+for+DERBY-4008"></a>
 <h4>Note for DERBY-4008</h4>
-<a name="N10C4A"></a><a name="Summary+of+Change-N10C4A"></a>
+<a name="N10C27"></a><a name="Summary+of+Change-N10C27"></a>
 <h5>Summary of Change</h5>
 <p>After the change for DERBY-4008, applications may see a different error message when attempting to connect a 10.5 client to older revision servers (e.g. 10.4 and 10.3) with multibyte database names.</p>
-<a name="N10C50"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10C50"></a>
+<a name="N10C2D"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10C2D"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In previous releases when attempting to connect to network server using a multibyte database name the connect would fail with the the exception:<br> 
 <span class="codefrag">SQLSTATE:22005 java.sql.SQLDataException: Unicode string cannot convert to Ebcdic string</span>
@@ -1811,64 +1801,64 @@
 <br> with a chained SQLException:<br> 
 <span class="codefrag">SQLSTATE:22005 java.sql.SQLDataException: Unicode string cannot convert to Ebcdic string</span>
 <br> The protocol error will also show on the server console.</p>
-<a name="N10C68"></a><a name="Incompatibilities+with+Previous+Release-N10C68"></a>
+<a name="N10C45"></a><a name="Incompatibilities+with+Previous+Release-N10C45"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>The client error message when attempting to connect with multibyte database names will change with mixed revision client/server as described in the previous section.</p>
-<a name="N10C6E"></a><a name="Rationale+for+Change-N10C6E"></a>
+<a name="N10C4B"></a><a name="Rationale+for+Change-N10C4B"></a>
 <h5>Rationale for Change</h5>
 <p>This change was made in preparation for fixing DERBY-728 to allow multibyte characters in the database name. The change in error message with back revision servers was considered an acceptable change and necessary to fix DERBY-728.</p>
-<a name="N10C74"></a><a name="Application+Changes+Required-N10C74"></a>
+<a name="N10C51"></a><a name="Application+Changes+Required-N10C51"></a>
 <h5>Application Changes Required</h5>
 <p>To reveert to the previous error message, users can upgrade their server to the latest on the 10.3 or 10.4 branch, or upgrade their server to 10.5. Otherwise applications expecting the old error message should upon gettting the SQLState: 08006 message retrieve the chained exception with SQLExcepiton.getNextMessage() and then process the message as before.</p>
 <hr>
-<a name="N10C7B"></a><a name="Note+for+DERBY-3977"></a>
+<a name="N10C58"></a><a name="Note+for+DERBY-3977"></a>
 <h4>Note for DERBY-3977</h4>
-<a name="N10C81"></a><a name="Summary+of+Change-N10C81"></a>
+<a name="N10C5E"></a><a name="Summary+of+Change-N10C5E"></a>
 <h5>Summary of Change</h5>
 <p>A different exception is thrown by the embedded driver when trying to truncate a Clob with a too large length argument.</p>
-<a name="N10C87"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10C87"></a>
+<a name="N10C64"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10C64"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, the embedded driver would throw an exception with SQLState XJ076 when trying to truncate a Clob with a length argument bigger than the Clob length. Now, it will throw the same exception as the client driver, XJ079. The error messages also differ:</p>
 <pre>Before: XJ076: The position argument '18149' exceeds the size of the BLOB/CLOB.
 Now: XJ079: The length specified '18149' exceeds the size of the BLOB/CLOB.
 </pre>
-<a name="N10C8F"></a><a name="Incompatibilities+with+Previous+Release-N10C8F"></a>
+<a name="N10C6C"></a><a name="Incompatibilities+with+Previous+Release-N10C6C"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Applications catching a specific exception based on SQLState may behave differently. The incompatibility can only be seen if the application calls <span class="codefrag">Clob.truncate</span> with the embedded driver.</p>
-<a name="N10C98"></a><a name="Rationale+for+Change-N10C98"></a>
+<a name="N10C75"></a><a name="Rationale+for+Change-N10C75"></a>
 <h5>Rationale for Change</h5>
 <p>To make the embedded and the client driver consistent.</p>
-<a name="N10C9E"></a><a name="Application+Changes+Required-N10C9E"></a>
+<a name="N10C7B"></a><a name="Application+Changes+Required-N10C7B"></a>
 <h5>Application Changes Required</h5>
 <p>Look for SQLState XJ079 instead of XJ076 when <span class="codefrag">Clob.truncate()</span> is called.</p>
 <hr>
-<a name="N10CA8"></a><a name="Note+for+DERBY-3701"></a>
+<a name="N10C85"></a><a name="Note+for+DERBY-3701"></a>
 <h4>Note for DERBY-3701</h4>
-<a name="N10CAE"></a><a name="Summary+of+Change-N10CAE"></a>
+<a name="N10C8B"></a><a name="Summary+of+Change-N10C8B"></a>
 <h5>Summary of Change</h5>
 <p>An error message will be logged to derby.log if the Network Server tracing file cannot be created. Starting with version 10.5, the Network Server will attempt to create the trace directory if it does not exist. Any intervening directories in the given path will also be created if possible.</p>
-<a name="N10CB4"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10CB4"></a>
+<a name="N10C91"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10C91"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Before the fix for DERBY-3110, if derby.drda.traceAll was set to true and the derby.drda.traceDirectory was set to a non-existent directory, no tracing would occur and no error would occur. After the fix for DERBY-3110, an error "java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept connections" would occur and the client would hang and no tracing would occur. With this fix for version 10.5 and higher, the Network Server will attempt to create the trace directory if possible. For 10.4.2 (and the next release on the 10.3 branch), the Network Server will still not try to create the directory. For all these releases the Network Server will print an error on session connect if there is any problem creating the trace file, but the Network Server will not cause the session connection to fail. Users who have trace turned on and the trace directory set to a non-existent directory may now see exceptions in the derby.log on connect indicating that the trace file is not found 
 <strong>or</strong> with 10.5 or higher they may see tracing occur where it did not before.</p>
-<a name="N10CBD"></a><a name="Incompatibilities+with+Previous+Release-N10CBD"></a>
+<a name="N10C9A"></a><a name="Incompatibilities+with+Previous+Release-N10C9A"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Tracing properties will not be ignored or cause the client to hang if the trace directory is set to a non-existent directory.</p>
-<a name="N10CC3"></a><a name="Rationale+for+Change-N10CC3"></a>
+<a name="N10CA0"></a><a name="Rationale+for+Change-N10CA0"></a>
 <h5>Rationale for Change</h5>
 <p>The tracing properties should not be summarily ignored or cause the client to hang if the trace directory does not exist.</p>
-<a name="N10CC9"></a><a name="Application+Changes+Required-N10CC9"></a>
+<a name="N10CA6"></a><a name="Application+Changes+Required-N10CA6"></a>
 <h5>Application Changes Required</h5>
 <p>Applications that counted on the derby.drda.traceAll property being ignored if derby.drda.traceDirectory was set to a non-existent directory, need to turn tracing off or they may now see many errors in the derby.log or large amounts of tracing.</p>
 <hr>
-<a name="N10CD0"></a><a name="Note+for+DERBY-3652"></a>
+<a name="N10CAD"></a><a name="Note+for+DERBY-3652"></a>
 <h4>Note for DERBY-3652</h4>
-<a name="N10CD6"></a><a name="Summary+of+Change-N10CD6"></a>
+<a name="N10CB3"></a><a name="Summary+of+Change-N10CB3"></a>
 <h5>Summary of Change</h5>
 <p>Derby now follows the SQL Standard rules for matching functions and procedures to Java methods.</p>
-<a name="N10CDC"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10CDC"></a>
+<a name="N10CB9"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10CB9"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In previous releases, Derby matched SQL routines to Java methods using an irregular set of rules which were hard to describe. At the same time, the user documentation falsely claimed that Derby followed the signature matching rules in the ANSI/ISO SQL Standard. Derby now conforms to the Standard behavior. In general, the Standard behavior is easier to understand and it is now possible to be confident that a function or procedure definition will match the desired Java method. In certain corner cases, however, methods which used to resolve will no longer resolve. The Standard resolution rules are described in the Derby Reference Guide.</p>
-<a name="N10CE2"></a><a name="Incompatibilities+with+Previous+Release-N10CE2"></a>
+<a name="N10CBF"></a><a name="Incompatibilities+with+Previous+Release-N10CBF"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Routines may resolve differently. Here are the differences listed in declining order of likelihood:</p>
 <ol>
@@ -1896,10 +1886,10 @@
 </ul>
 </li>
 </ol>
-<a name="N10D2C"></a><a name="Rationale+for+Change-N10D2C"></a>
+<a name="N10D09"></a><a name="Rationale+for+Change-N10D09"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behavior violated the SQL Standard and was very hard to explain. The new behavior is correct and easy to describe.</p>
-<a name="N10D32"></a><a name="Application+Changes+Required-N10D32"></a>
+<a name="N10D0F"></a><a name="Application+Changes+Required-N10D0F"></a>
 <h5>Application Changes Required</h5>
 <p>This release includes a lint tool, <em>SignatureChecker</em>. If your application uses SQL functions and/or procedures, you should run this tool against your databases in order to find routines which no longer match. To run the tool, make sure that your classpath contains the 10.5 jar files, including <em>derbytools.jar</em>.</p>
 <p>On a J2SE platform, run the lint tool as follows (where CONNECTION_URL_TO_DATABASE is the connection URL you would use in order to obtain a connection via <em>DriverManager.getConnection()</em>):</p>
@@ -1936,30 +1926,30 @@
 <strong>Routine</strong> - Drop and recreate your function/procedure so that its arguments and return type match your Java method according to the Standard rules described in the Reference Guide.</li>
 </ol>
 <hr>
-<a name="N10D69"></a><a name="Note+for+DERBY-3420"></a>
+<a name="N10D46"></a><a name="Note+for+DERBY-3420"></a>
 <h4>Note for DERBY-3420</h4>
-<a name="N10D6F"></a><a name="Summary+of+Change-N10D6F"></a>
+<a name="N10D4C"></a><a name="Summary+of+Change-N10D4C"></a>
 <h5>Summary of Change</h5>
 <p>The <em>-ca</em> command line option has been removed from ij.</p>
-<a name="N10D78"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10D78"></a>
+<a name="N10D55"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10D55"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Applications which attempt to pass JDBC connection attributes using the -ca flag to ij will be rejected, with a usage message such as: Usage: java org.apache.derby.tools.ij -p propertyfile inputfile</p>
-<a name="N10D7E"></a><a name="Incompatibilities+with+Previous+Release-N10D7E"></a>
+<a name="N10D5B"></a><a name="Incompatibilities+with+Previous+Release-N10D5B"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Applications which attempt to pass JDBC connection attributes using the -ca flag to ij will fail, as that flag is no longer recognized by ij.</p>
-<a name="N10D84"></a><a name="Rationale+for+Change-N10D84"></a>
+<a name="N10D61"></a><a name="Rationale+for+Change-N10D61"></a>
 <h5>Rationale for Change</h5>
 <p>It used to be that you could not specify both client and embedded attributes in the connection URL. Since Derby now supports such combinations of attributes in the connection URL, the community decided that the -ca option doesn't really add value and so it has been removed.</p>
-<a name="N10D8A"></a><a name="Application+Changes+Required-N10D8A"></a>
+<a name="N10D67"></a><a name="Application+Changes+Required-N10D67"></a>
 <h5>Application Changes Required</h5>
 <p>Applications should include connection attributes in the connection URL. For example: connect 'jdbc:derby:myDB;territory=no_NO;collation=TERRITORY_BASED;create=true';</p>
 <hr>
-<a name="N10D91"></a><a name="Note+for+DERBY-3347"></a>
+<a name="N10D6E"></a><a name="Note+for+DERBY-3347"></a>
 <h4>Note for DERBY-3347</h4>
-<a name="N10D97"></a><a name="Summary+of+Change-N10D97"></a>
+<a name="N10D74"></a><a name="Summary+of+Change-N10D74"></a>
 <h5>Summary of Change</h5>
 <p>A bug that could cause unrecoverable database corruption has been fixed.</p>
-<a name="N10D9D"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10D9D"></a>
+<a name="N10D7A"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10D7A"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>A bug that could cause database corruption was introduced in the 10.3 codeline and affects the following releases:</p>
 <ul>
@@ -1973,59 +1963,59 @@
 ERROR XSDG3: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@1afb0c7 could not be accessed
 ERROR XSLA1: Log Record has been sent to the stream, but it cannot be applied to the store (Object null). This may cause recovery problems also.
 </pre>
-<a name="N10DAC"></a><a name="Incompatibilities+with+Previous+Release-N10DAC"></a>
+<a name="N10D89"></a><a name="Incompatibilities+with+Previous+Release-N10D89"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None.</p>
-<a name="N10DB2"></a><a name="Rationale+for+Change-N10DB2"></a>
+<a name="N10D8F"></a><a name="Rationale+for+Change-N10D8F"></a>
 <h5>Rationale for Change</h5>
 <p>Database corruption is bad.</p>
-<a name="N10DB8"></a><a name="Application+Changes+Required-N10DB8"></a>
+<a name="N10D95"></a><a name="Application+Changes+Required-N10D95"></a>
 <h5>Application Changes Required</h5>
 <p>No changes are required. However, since the database corruption may go unnoticed for a while, users may want to check the consistency of their databases after upgrading Derby. The process is described on the following wiki page: <a class="external" href="http://wiki.apache.org/db-derby/DatabaseConsistencyCheck">http://wiki.apache.org/db-derby/DatabaseConsistencyCheck</a> . If a corruption is detected, restoring the database from backup is the only reliable way to recover.</p>
 <hr>
-<a name="N10DC3"></a><a name="Note+for+DERBY-3327"></a>
+<a name="N10DA0"></a><a name="Note+for+DERBY-3327"></a>
 <h4>Note for DERBY-3327</h4>
-<a name="N10DC9"></a><a name="Summary+of+Change-N10DC9"></a>
+<a name="N10DA6"></a><a name="Summary+of+Change-N10DA6"></a>
 <h5>Summary of Change</h5>
 <p>The effect of setting the current default schema (<span class="codefrag">SET SCHEMA schemaname</span>) inside nested connection of a stored procedure or function has been changed to comply with SQL standard semantics.</p>
 <p>Previously, setting the schema in a nested connection would have an effect on the current default schema also in the SQL connection of the caller. The SQL standard requires that the value of the default current schema at the time of the call be reestablished when the call is completed. This is now implemented.</p>
 <p>If the current schema is dropped by a stored procedure or function, the current schema as well as the saved values of the callers will be reset to the initial default schema of the root connection.</p>
-<a name="N10DD6"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10DD6"></a>
+<a name="N10DB3"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10DB3"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N10DDA"></a><a name="Rationale+for+Change-N10DDA"></a>
+<a name="N10DB7"></a><a name="Rationale+for+Change-N10DB7"></a>
 <h5>Rationale for Change</h5>
 <p>SQL standard compliance.</p>
-<a name="N10DE0"></a><a name="Application+Changes+Required-N10DE0"></a>
+<a name="N10DBD"></a><a name="Application+Changes+Required-N10DBD"></a>
 <h5>Application Changes Required</h5>
 <hr>
-<a name="N10DE5"></a><a name="Note+for+DERBY-3319"></a>
+<a name="N10DC2"></a><a name="Note+for+DERBY-3319"></a>
 <h4>Note for DERBY-3319</h4>
-<a name="N10DEB"></a><a name="Summary+of+Change-N10DEB"></a>
+<a name="N10DC8"></a><a name="Summary+of+Change-N10DC8"></a>
 <h5>Summary of Change</h5>
 <p>Exception is thrown when connection with uncommitted operations is closed.</p>
-<a name="N10DF1"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10DF1"></a>
+<a name="N10DCE"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10DCE"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, applications could close a connection obtained from Derby's implementations of <span class="codefrag">javax.sql.DataSource</span> or <span class="codefrag">javax.sql.ConnectionPoolDataSource</span>, even if the connection had uncommitted operations. Now, Derby raises an <span class="codefrag">SQLException</span> when an attempt to close a connection with an active transaction is made. The exception will have SQLState 25001, and its message will say the following:</p>
 <pre>java.sql.SQLException: Cannot close a connection while a transaction is still active.
 </pre>
-<a name="N10E02"></a><a name="Incompatibilities+with+Previous+Release-N10E02"></a>
+<a name="N10DDF"></a><a name="Incompatibilities+with+Previous+Release-N10DDF"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Applications that close connections with active transactions now fail.</p>
-<a name="N10E08"></a><a name="Rationale+for+Change-N10E08"></a>
+<a name="N10DE5"></a><a name="Rationale+for+Change-N10DE5"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behaviour was not consistent with the behaviour of connection objects obtained from <span class="codefrag">java.sql.DriverManager</span>, which already raise an exception in such a situation. The previous behaviour could also cause resource leaks because there is no way to free the resources held by an active transaction once its connection object has been closed.</p>
-<a name="N10E11"></a><a name="Application+Changes+Required-N10E11"></a>
+<a name="N10DEE"></a><a name="Application+Changes+Required-N10DEE"></a>
 <h5>Application Changes Required</h5>
 <p>Users must call <span class="codefrag">commit()</span> or <span class="codefrag">rollback()</span>, or use auto-commit, before attempting to close a connection with uncommitted operations.</p>
 <hr>
-<a name="N10E1E"></a><a name="Note+for+DERBY-2351"></a>
+<a name="N10DFB"></a><a name="Note+for+DERBY-2351"></a>
 <h4>Note for DERBY-2351</h4>
-<a name="N10E24"></a><a name="Summary+of+Change-N10E24"></a>
+<a name="N10E01"></a><a name="Summary+of+Change-N10E01"></a>
 <h5>Summary of Change</h5>
 <p>An ORDER BY clause of a DISTINCT query which specifies to order by a column which was not in the DISTINCT list is now rejected, because the intent of the query is ambiguous. Previously, Derby instead produced non-distinct results. Also, an ORDER BY clause which specifies a table-name-qualified column alias is now rejected as invalid, where previously it was accepted.</p>
-<a name="N10E2A"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10E2A"></a>
+<a name="N10E07"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10E07"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N10E2E"></a><a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
+<a name="N10E0B"></a><a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
 <h5>New rules for DISTINCT and ORDER BY</h5>
 <p>Applications which specify certain combinations of SELECT DISTINCT with ORDER BY will now receive an error message, whereas formerly such applications received non-distinct results.</p>
 <p>As an example, take the following:</p>
@@ -2034,7 +2024,7 @@
 </p>
 <p>The query above is now rejected, with the error message:</p>
 <p>If the AGE column is included in the DISTINCT list in the above query, there is no ambiguity</p>
-<a name="N10E46"></a><a name="New+column+alias+rules"></a>
+<a name="N10E23"></a><a name="New+column+alias+rules"></a>
 <h5>New column alias rules</h5>
 <p>Applications which specify a column alias for a column in the SELECT statement, and which specify an ORDER BY clause which specifies that column alias qualified by the table name, will now receive an error indicating that the ORDER BY clause is invalid.</p>
 <p>As an example, take the following:</p>
@@ -2044,7 +2034,7 @@
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by idcolumn1, idcolumn2;</p>
 <p>or</p>
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.id, t1.id;</p>
-<a name="N10E5C"></a><a name="Rationale+for+Change-N10E5C"></a>
+<a name="N10E39"></a><a name="Rationale+for+Change-N10E39"></a>
 <h5>Rationale for Change</h5>
 <p>When the query ambiguously specifies both DISTINCT and ORDER BY, Derby was unsure whether to return the rows properly ordered, but non-distinct, or to return a distinct set of rows, but in an unknown order. Since no clear resolution of the ambiguity could be found, we chose instead to reject the query.</p>
 <p>The rules for resolving column references in ORDER BY clauses have been enhanced to consider column aliases and column names more fully. Derby now uses different resolution rules depending on whether the ORDER BY column reference is table.column, or just column:</p>
@@ -2054,14 +2044,14 @@
 </ul>
 <br>
 <br>
-<a name="N10E6B"></a><a name="Application+Changes+Required-N10E6B"></a>
+<a name="N10E48"></a><a name="Application+Changes+Required-N10E48"></a>
 <h5>Application Changes Required</h5>
 <p>A query which specifies ordering by a non-distinct column should instead include the ORDER BY column in the DISTINCT list, to resolve the ambiguity about which values of that column should be used to distinctly identify the resulting rows.</p>
 <p>A query which specifies table-name.alias-name should be rewritten to specify either simply alias-name, or table-name.column-name.</p>
 <hr>
-<a name="N10E74"></a><a name="Note+for+DERBY-2085"></a>
+<a name="N10E51"></a><a name="Note+for+DERBY-2085"></a>
 <h4>Note for DERBY-2085</h4>
-<a name="N10E7A"></a><a name="Summary+of+Change-N10E7A"></a>
+<a name="N10E57"></a><a name="Summary+of+Change-N10E57"></a>
 <h5>Summary of Change</h5>
 <p>Derby has improved the error message which is issued when an invalid column reference is found in a grouped query. Derby now issues message 42Y36 instead of 42Y30. Furthermore, the wording of message 42Y36 has been expanded to further explain the behavior.</p>
 <p>Consider the table</p>
@@ -2071,53 +2061,53 @@
 <p>In Derby releases 10.2, 10.3, and 10.4, this query gives the following error message:</p>
 <span class="codefrag">ERROR 42Y30: The SELECT list of a grouped query contains at least one invalid expression. If a SELECT list has a GROUP BY, the list may only contain valid grouping expressions and valid aggregate expressions.</span>
 <p>This is misleading since there is no invalid expression in the SELECT list. It is the ORDER BY clause that is wrong. In Derby 10.5, this query will now give the following error message, which is a revised version of the message issued by 10.1 (that is, Derby 10.5 behaves more like Derby 10.1 in this respect):</p>
-<span class="codefrag">ERROR 42Y36: Column reference 'J' is invalid, or is part of an invalid expression. For a SELECT list with a GROUP BY, the columns and expressions being selected may only contain valid grouping expressions and valid aggregate expressions.</span><a name="N10E90"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10E90"></a>
+<span class="codefrag">ERROR 42Y36: Column reference 'J' is invalid, or is part of an invalid expression. For a SELECT list with a GROUP BY, the columns and expressions being selected may only contain valid grouping expressions and valid aggregate expressions.</span><a name="N10E6D"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10E6D"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>An application which issued a grouped select statement with an invalid column reference in the order by clause may now receive a different error message than it did in 10.4.</p>
-<a name="N10E96"></a><a name="Rationale+for+Change-N10E96"></a>
+<a name="N10E73"></a><a name="Rationale+for+Change-N10E73"></a>
 <h5>Rationale for Change</h5>
 <p>We feel that message 42Y36 is more helpful to the user in explaining the problem with the invalid query.</p>
 <hr>
-<a name="N10E9D"></a><a name="Note+for+DERBY-1062"></a>
+<a name="N10E7A"></a><a name="Note+for+DERBY-1062"></a>
 <h4>Note for DERBY-1062</h4>
-<a name="N10EA3"></a><a name="Summary+of+Change-N10EA3"></a>
+<a name="N10E80"></a><a name="Summary+of+Change-N10E80"></a>
 <h5>Summary of Change</h5>
 <p>Applications will see a different error code and message when they attempt to call SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE on a table that does not exist.</p>
-<a name="N10EA9"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10EA9"></a>
+<a name="N10E86"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10E86"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Applications will see a different error code and message when they attempt to call SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE on a table that does not exist. The new error code and message will be ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'MissingTableName' because it does not exist. The old error code and message used to be ERROR 42X05: Table/View 'MissingTableName' does not exist.</p>
-<a name="N10EAF"></a><a name="Incompatibilities+with+Previous+Release-N10EAF"></a>
+<a name="N10E8C"></a><a name="Incompatibilities+with+Previous+Release-N10E8C"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>The SQL exception code in the previous release was 42X05 and error message was "Table/View 'MissingTableName' does not exist."</p>
-<a name="N10EB5"></a><a name="Rationale+for+Change-N10EB5"></a>
+<a name="N10E92"></a><a name="Rationale+for+Change-N10E92"></a>
 <h5>Rationale for Change</h5>
 <p>To avoid duplication of code, the error handling is now done by a generic routine in ALTER TABLE rather than a routine specific to SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE. This change to use ALTER TABLE code to implement SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE was made in 10.5 release and that is the reason behind the change in error code behavior.</p>
-<a name="N10EBB"></a><a name="Application+Changes+Required-N10EBB"></a>
+<a name="N10E98"></a><a name="Application+Changes+Required-N10E98"></a>
 <h5>Application Changes Required</h5>
 <p>If the application is looking for 42X05, it should be changed to look for 42Y55.</p>
 <hr>
-<a name="N10EC2"></a><a name="Note+for+DERBY-48"></a>
+<a name="N10E9F"></a><a name="Note+for+DERBY-48"></a>
 <h4>Note for DERBY-48</h4>
-<a name="N10EC8"></a><a name="Summary+of+Change-N10EC8"></a>
+<a name="N10EA5"></a><a name="Summary+of+Change-N10EA5"></a>
 <h5>Summary of Change</h5>
 <p>In Derby, a user's <strong>initial default schema</strong> is named the same as the user name, or APP if a user is not provided at connect time. This schema is implicitly auto-created the first time a schema object is created in that schema.</p>
 <p>Previously, this auto-creation would be performed as part of the user transaction. This would sometimes lead to locking issues as described in this issue. With this change, the auto-creation is now performed and committed immediately in a separate sub-transaction.</p>
-<a name="N10ED3"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10ED3"></a>
+<a name="N10EB0"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10EB0"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>The initial default schema will be present in cases where it previously would not yet have been created: If the user transaction that creates a schema object leading to auto-creation of the initial default schema rolls back for some reason after having created the schema, up till now the auto-creation of the initial default schema would be rolled back as well. Since it is now created and committed in a sub-transaction, the schema creation will not be rolled back: the default schema will persist.</p>
-<a name="N10ED9"></a><a name="Incompatibilities+with+Previous+Release-N10ED9"></a>
+<a name="N10EB6"></a><a name="Incompatibilities+with+Previous+Release-N10EB6"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Most applications should not be impacted by this change, but there are some corner cases as described below:</p>
 <p>If the application tests for the existence of the initial default schema by querying Derby system tables, the results could now be different than in earlier releases, if the test is made after a rollback as described in the previous section.</p>
 <p>Since the initial default schema will now potentially exist in cases where it would previously not exist, schema operations may be impacted, e.g. where before a DROP SCHEMA &lt;default schema name&gt; RESTRICT would fail due to it not yet existing, it could now work (if empty), depending on when the drop attempt is made.</p>
-<a name="N10EE3"></a><a name="Rationale+for+Change-N10EE3"></a>
+<a name="N10EC0"></a><a name="Rationale+for+Change-N10EC0"></a>
 <h5>Rationale for Change</h5>
 <p>Implicit schema creation is now performed in its own transaction to avoid deadlocks with other connections accessing the same schema.</p>
 <p>Doing this is a separate transaction avoids holding dictionary locks longer than necessary, cf. <a class="external" href="https://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a> and thus reduces the chance for deadlocks.</p>
-<a name="N10EEF"></a><a name="Application+Changes+Required-N10EEF"></a>
+<a name="N10ECC"></a><a name="Application+Changes+Required-N10ECC"></a>
 <h5>Application Changes Required</h5>
 <p>Verify that the application code does not rely on the initial default schema being absent after a rollback.</p>
-<a name="N10EF5"></a><a name="Build+Environment"></a>
+<a name="N10ED2"></a><a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <p>Derby release 10.5.1.1 was built using the following environment:</p>
 <ul>
@@ -2137,7 +2127,7 @@
 <strong>JSR 169</strong> - J2ME support was built using IBM's j9 jvm from WEME6.1</li>
 </ul>
 </div>
-<a name="N10F1A"></a><a name="Verifying+releases"></a>
+<a name="N10EF7"></a><a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>
@@ -2160,14 +2150,14 @@
 <p>We strongly recommend you verify your downloads with both PGP and MD5.</p>
 </div>
 </div>
-<!--+
-    |end content
+<!--+
+    |end content
     +-->
 <div class="clearboth">&nbsp;</div>
 </div>
 <div id="footer">
-<!--+
-    |start bottomstrip
+<!--+
+    |start bottomstrip
     +-->
 <div class="lastmodified">
 <script type="text/javascript"><!--
@@ -2181,8 +2171,8 @@
     Send feedback about the website to:
   <a id="feedbackto" href="mailto:derby-user@db.apache.org?subject=Feedback%C2%A0releases/release-10.5.1.1.html">derby-user@db.apache.org</a>
 </div>
-<!--+
-    |end bottomstrip
+<!--+
+    |end bottomstrip
     +-->
 </div>
 </body>

Added: db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi?rev=799768&view=auto
==============================================================================
--- db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi (added)
+++ db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi Fri Jul 31 23:04:15 2009
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.    
+
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+#  python includes correctly)
+# Copied from Stefan's http://www.apache.org/~bodewig/mirror.html
+cd /www/www.apache.org/dyn/mirrors 
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*

Propchange: db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: db/derby/site/trunk/build/site/releases/release-10.5.2.0.cgi
------------------------------------------------------------------------------
    svn:executable = *



Mime
View raw message