[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]

Myrna van Lunteren updated DERBY-1746:
--------------------------------------

    Attachment: DERBY-1746_102_20060823.stat
                DERBY-1746_102_20060823.diff
                DERBY-1746_trunk_20060824.diff

Attaching patches for this - DERBY-1746_102_20060823.diff modifies the master & 
updates the snv:externals property for the directory 
<10.2>/tools/testing/derby, and DERBy-1746_trunk_20060823.diff does the same 
for the trunk.

The trunk patch is a bit odd because I made a manual change - when I run the 
test right now it fails because of failing version compare tests. I think these 
diffs are to be expected currently, but I did not want to check that in as a 
master, I think that needs to be looked at separately...It seems as the trunk 
is no longer 10.2 this test needs to get changed/renamed, and I didn't want to 
address that here.

I assume patch or eclipse-apply-patch won't deal with the changing of 
properties, so here is the svn command:
(when cd-ed to the top of the branch)
cd tools/testing
svn propedit svn:externals derby
& change to:
derby/10.1 https://svn.apache.org/repos/asf/db/derby/jars/10.1.3.1
(note: svn update required after to see the files changed)

Thx to andrew for adding the 10.1.3.1 jars already.




> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
>                 Key: DERBY-1746
>                 URL: http://issues.apache.org/jira/browse/DERBY-1746
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.1.0
>            Reporter: Myrna van Lunteren
>         Assigned To: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.2.1.0
>
>         Attachments: DERBY-1746_102_20060823.diff, 
> DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn -  
> 10.1.1.0 - (208786). 
> However, we now have a newer released version of 10.1 - 10.1.3.  This would 
> be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for 
> DERBY-655:
> 703d702
> < 
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,
>  7
> 2168d2166
> < 
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,
>  7
> It would be nice if the final build for 10.2 would include an updgrade test 
> master created using 10.1.3, And same is true for the trunk.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to