[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495809 ]
Myrna van Lunteren commented on DERBY-1746: ------------------------------------------- I think, this is now a mute point - or it's fixed by Dan (by converting the test). However, we should now to remove the svn:externals dependency on the for 10.1, or, better still, to automatically add an svn;externals into our trunk for 10.3.1.0 ... etc... Thoughts? > upgrade tests should start using 10.1.3 released builds > ------------------------------------------------------- > > Key: DERBY-1746 > URL: https://issues.apache.org/jira/browse/DERBY-1746 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.2.1.6 > Reporter: Myrna van Lunteren > Priority: Minor > 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. - You can reply to this email to add a comment to the issue online.