Yes!
I have just added a new patch which contains the svn property change.
Suresh,
Thanks for your comments on this bug. I just updated the patch and saw
your comments. I will now look into them and post the next version of patch.
Thank you guyz for looking into this.
Mayuresh
Andrew McIntyre wrote:
On 11/30/06, Suresh Thalamati <[EMAIL PROTECTED]> wrote:
Andrew McIntyre (JIRA) wrote:
>
> The 10.2.1.6 jars are checked into the repository and available at
http://svn.apache.org/repos/asf/db/derby/jars/10.2.1.6/. 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/10.2.1.6
>
> The next time you do an svn update, the 10.2.1.6 jars will be
checked out to tools/testing/derby/10.2
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.
No particular reason, other than there is not yet a test checked in
which requires the 10.2 jar files.
A commit which introduces a new test that requires the 10.2 jar files
should also include the necessary svn property change to check out the
10.2 jars into the local checkout as described above.
andrew
