db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Thalamati <suresh.thalam...@gmail.com>
Subject Re: [jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
Date Fri, 01 Dec 2006 07:40:00 GMT
Andrew McIntyre (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12454250 ]

> Andrew McIntyre commented on DERBY-606:
> ---------------------------------------
> The jars are checked into the repository and available at http://svn.apache.org/repos/asf/db/derby/jars/
To add them to a trunk checkout, execute the following from the top of a checkout of the trunk:
> svn pe svn:externals tools/testing
> and then add a line for the 10.2 jars, e.g.:
> derby/10.2 https://svn.apache.org/repos/asf/db/derby/jars/
> The next time you do an svn update, the jars will be checked out to tools/testing/derby/10.2


Thanks for adding the 10.2 jar files to the trunk.  I tried the above 
instructions , they worked great.

If Mayuresh adds Upgrade_10_2_10_3.java test to upgrade.runall. Then 
it is likely to  fail if some one does a simple svn update, without 
following the above instructions.   Just curious any particular reason 
why these special commands are required to fetch the 10.2 jars to an 
existing client instead of simple "svn update" command.


View raw message