db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1746) upgrade tests should start using 10.1.3 released builds
Date Fri, 05 Jan 2007 02:36:27 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462385
] 

Andrew McIntyre commented on DERBY-1746:
----------------------------------------

I took a look at this issue and I've come to an impasse. The sealing problem that Myrna encountered
is due to the fact that the 10.1.3.1 jars, unlike the 10.1.1.0 jars, are sealed. When running
from the classes directory, UpgradeTester puts the entire classes directory into the ClassLoader
because it needs some of the testing classes from the newer version. Unfortunately, this also
puts all of the newer Derby classes into the classloader's classpath along with the sealed
Derby jars. When the engine is booted, attempting to boot the services causes the sealing
exception to be thrown. This is not a problem when running the test from jars because only
derbyTesting.jar is made available to the old classloader, so there is not a sealing exception.


I think the thing to do is to create a custom ClassLoader that will only load classes from
org.apache.derbyTesting, and then make this the parent of oldClassLoader, so that classes
from org.apache.derbyTesting are loaded from the classes directory, and all other classes
are loaded from the old jars when running the phases of the test with oldClassLoader. Despite
my best efforts to subclass URLClassLoader to do this, I could not get it to cooperate. I'll
come back to this at a later date, but am not planning on investigating it further at this
time.


> 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

        

Mime
View raw message