[
https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462416
]
Daniel John Debrunner commented on DERBY-1746:
----------------------------------------------
I'm working on an approach for this where the testing classes are always loaded
from the "new" class loader and only the database code is loaded from the old
loader. However it's much cleaner to do this in the pure junit world so I'm
also experimenting with converting the upgrade tests to Junit.
The change involves making the code that loads the data source use the thread
context loader instead of just Class.forName.
> 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
> Fix For: 10.2.3.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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
