You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/03/03 22:35:39 UTC
[jira] Created: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Combine the script and the test available for upgrade testing into a java test
------------------------------------------------------------------------------
Key: DERBY-1075
URL: http://issues.apache.org/jira/browse/DERBY-1075
Project: Derby
Type: Sub-task
Reporter: Deepa Remesh
Priority: Minor
Fix For: 10.2.0.0
Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
David Van Couvering updated DERBY-1075:
---------------------------------------
Attachment: classloader.jar
Hi, Deepa. This is a copy of engine/org/apache/derby/jdbc in my sandbox. DerbyLoader.jar is a classloader I wrote to handle code sharing. You will notice that there are two things going on:
- A number of the classes have been split up into a "proxy" and its underlying implementation that it delegates to
- The underlying implementation implements an interface defined in the "interfaces" package. The interfaces need to be a separate package to avoid sealing issues
- The proxy class loads the implementation class using DerbyLoader and then casts it to the appropriate interface, and then invokes methods via that interface.
Let me know if you have any questions. It's been a while since I worked on this but I think I can get the cogs working again if need be.
I have granted license for this in case Deepa wants to use some or all of this code herself, but in general it is *not* intended for checkin as is.
David
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
Re: [jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Hi, Yeradis. Thanks for your email. I'm glad you liked my blog --
thanks for your comment! It's great to get to know you, if only
electronically.
You can read 24 languages? Wow! Here in the USA it is so easy to be
lazy and just speak and read English. Even when you travel to other
places, so many people speak English, so it's hard to be motivated to
learn another language.
For example, if you haven't noticed, I work with a group of Norwegians,
and I go over to visit from time to time. I've wanted to learn
Norwegian, but every time I go over there, they speak such perfect
English, that it just seems silly for me to struggle along in Norwegian.
So I never learn it...
David
yeradis wrote:
> hi David
> i hope you and your family be ok really
>
> and this too for all the derby world ;-)
>
> i will not do that question about the backup system ;-) :-p
> because i'm the first person who dont use it and by that mistake , i los
> 6 months of work
> because i was trusted on hardware backup
> but with storm there is no way to trust in anything
> jajaajaja :-/ i luagh to no cry :-s
>
> by the way i was read the lines that are in your blog
>
> really , thanks to you and to every body that has the amiability to do
> this thinks
> i mean contributions to all us with some comment , some project
>
> and is true you are right , the english is not my language
> i speak and write it like a parrot (tucan for example)
> but i;m looky i read it very well ;-)
> thats enought starting in the way that i read 24 languages
> other not so good by i defend me in reading :-p
> and if i cant read something there is my good friend Google :-p with the
> translator ;-)
>
> thanks again
>
>
>
>
>
> On 3/22/06, *David W. Van Couvering* <David.Vancouvering@sun.com
> <ma...@sun.com>> wrote:
>
> Well that really, really sucks. It appears that my version of
> DerbyLoader.java on disk is corrupt, and that is my *only* copy. Don't
> get me started on why I don't yet have a working backup strategy.
>
> I know what I need to do and can do it again, but that was a lot of
> work
> down the drain. Sigh...
>
> Basically what I had written was a "child-first" classloader that loads
> from its search path *before* it loads from the parent. I don't think
> you really need that, Deepa, your classloader works fine. The usage of
> interfaces that you see in the rest of the code would work just as well
> for a standard URLClassLoader.
>
> David
>
> Deepa Remesh (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
> >
> > Deepa Remesh updated DERBY-1075:
> > --------------------------------
> >
> > Attachment: derby-1075-v2.diff
> > derby-1075-v2.status
> >
> > Thanks Andreas for pointing out the new case added to
> phaseTester. I had not noticed the change as it was committed after
> I uploaded my first patch. I have added this test to UpgradeTester
> and also updated the master. The new patch is uploaded as
> 'derby-1075-v2.diff'. With this patch, I have built and run the new
> upgrade test on WinXP using Sun JDK 1.4.2. Once this patch gets
> reviewed and committed, it will replace phaseTester.java and
> runPhases.ksh and we can remove these files.
> >
> > David, thanks for uploading your classloader work. I extracted
> the jar file using jar command but I find DerbyLoader.java in
> unreadable format. I am curious to understand what you have done but
> do not plan to work on it immediately. So whenever you get time,
> please check the jar file to see if you are able to read
> DerbyLoader.java.
> >
> >
> >>Combine the script and the test available for upgrade testing
> into a java test
> >>------------------------------------------------------------------------------
> >>
> >> Key: DERBY-1075
> >> URL: http://issues.apache.org/jira/browse/DERBY-1075
> >> Project: Derby
> >> Type: Sub-task
> >> Reporter: Deepa Remesh
> >> Assignee: Deepa Remesh
> >> Priority: Minor
> >> Fix For: 10.2.0.0 <http://10.2.0.0>
> >> Attachments: classloader.jar, derby-1075-patch1-draft.diff,
> derby-1075-patch1-draft.status, derby-1075-v1.diff,
> derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status,
> loader.java, loader_v2.java
> >>
> >>Separating a part of DERBY-514 into a sub-task. This sub-task is
> to combine the script 'runphases.ksh' and the java file
> 'phaseTester.java' into a single java test. This will help to later
> add the upgrade tests into the regression suite. Also, this sub-task
> can be done independent of DERBY-1049 which is blocking DERBY-514.
> >
> >
>
>
>
Re: [jira] Updated: (DERBY-1075) Combine the script and the test available for upgrade testing into a java test
Posted by yeradis <ye...@gmail.com>.
hi David
i hope you and your family be ok really
and this too for all the derby world ;-)
i will not do that question about the backup system ;-) :-p
because i'm the first person who dont use it and by that mistake , i los 6
months of work
because i was trusted on hardware backup
but with storm there is no way to trust in anything
jajaajaja :-/ i luagh to no cry :-s
by the way i was read the lines that are in your blog
really , thanks to you and to every body that has the amiability to do this
thinks
i mean contributions to all us with some comment , some project
and is true you are right , the english is not my language
i speak and write it like a parrot (tucan for example)
but i;m looky i read it very well ;-)
thats enought starting in the way that i read 24 languages
other not so good by i defend me in reading :-p
and if i cant read something there is my good friend Google :-p with the
translator ;-)
thanks again
On 3/22/06, David W. Van Couvering <Da...@sun.com> wrote:
>
> Well that really, really sucks. It appears that my version of
> DerbyLoader.java on disk is corrupt, and that is my *only* copy. Don't
> get me started on why I don't yet have a working backup strategy.
>
> I know what I need to do and can do it again, but that was a lot of work
> down the drain. Sigh...
>
> Basically what I had written was a "child-first" classloader that loads
> from its search path *before* it loads from the parent. I don't think
> you really need that, Deepa, your classloader works fine. The usage of
> interfaces that you see in the rest of the code would work just as well
> for a standard URLClassLoader.
>
> David
>
> Deepa Remesh (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
> >
> > Deepa Remesh updated DERBY-1075:
> > --------------------------------
> >
> > Attachment: derby-1075-v2.diff
> > derby-1075-v2.status
> >
> > Thanks Andreas for pointing out the new case added to phaseTester. I had
> not noticed the change as it was committed after I uploaded my first patch.
> I have added this test to UpgradeTester and also updated the master. The new
> patch is uploaded as 'derby-1075-v2.diff'. With this patch, I have built
> and run the new upgrade test on WinXP using Sun JDK 1.4.2. Once this patch
> gets reviewed and committed, it will replace phaseTester.java and
> runPhases.ksh and we can remove these files.
> >
> > David, thanks for uploading your classloader work. I extracted the jar
> file using jar command but I find DerbyLoader.java in unreadable format. I
> am curious to understand what you have done but do not plan to work on it
> immediately. So whenever you get time, please check the jar file to see if
> you are able to read DerbyLoader.java.
> >
> >
> >>Combine the script and the test available for upgrade testing into a
> java test
>
> >>------------------------------------------------------------------------------
> >>
> >> Key: DERBY-1075
> >> URL: http://issues.apache.org/jira/browse/DERBY-1075
> >> Project: Derby
> >> Type: Sub-task
> >> Reporter: Deepa Remesh
> >> Assignee: Deepa Remesh
> >> Priority: Minor
> >> Fix For: 10.2.0.0
> >> Attachments: classloader.jar, derby-1075-patch1-draft.diff,
> derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status,
> derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
> >>
> >>Separating a part of DERBY-514 into a sub-task. This sub-task is to
> combine the script 'runphases.ksh' and the java file 'phaseTester.java'
> into a single java test. This will help to later add the upgrade tests into
> the regression suite. Also, this sub-task can be done independent of
> DERBY-1049 which is blocking DERBY-514.
> >
> >
>
>
>
Re: [jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by Kathey Marsden <km...@sbcglobal.net>.
David W. Van Couvering wrote:
> It appears that my version of DerbyLoader.java on disk is corrupt,
> and that is my *only* copy.
Yikes! Perhaps some other application that you used to access that file
hard upgraded it automatically.
Re: [jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Well that really, really sucks. It appears that my version of
DerbyLoader.java on disk is corrupt, and that is my *only* copy. Don't
get me started on why I don't yet have a working backup strategy.
I know what I need to do and can do it again, but that was a lot of work
down the drain. Sigh...
Basically what I had written was a "child-first" classloader that loads
from its search path *before* it loads from the parent. I don't think
you really need that, Deepa, your classloader works fine. The usage of
interfaces that you see in the rest of the code would work just as well
for a standard URLClassLoader.
David
Deepa Remesh (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
>
> Deepa Remesh updated DERBY-1075:
> --------------------------------
>
> Attachment: derby-1075-v2.diff
> derby-1075-v2.status
>
> Thanks Andreas for pointing out the new case added to phaseTester. I had not noticed the change as it was committed after I uploaded my first patch. I have added this test to UpgradeTester and also updated the master. The new patch is uploaded as 'derby-1075-v2.diff'. With this patch, I have built and run the new upgrade test on WinXP using Sun JDK 1.4.2. Once this patch gets reviewed and committed, it will replace phaseTester.java and runPhases.ksh and we can remove these files.
>
> David, thanks for uploading your classloader work. I extracted the jar file using jar command but I find DerbyLoader.java in unreadable format. I am curious to understand what you have done but do not plan to work on it immediately. So whenever you get time, please check the jar file to see if you are able to read DerbyLoader.java.
>
>
>>Combine the script and the test available for upgrade testing into a java test
>>------------------------------------------------------------------------------
>>
>> Key: DERBY-1075
>> URL: http://issues.apache.org/jira/browse/DERBY-1075
>> Project: Derby
>> Type: Sub-task
>> Reporter: Deepa Remesh
>> Assignee: Deepa Remesh
>> Priority: Minor
>> Fix For: 10.2.0.0
>> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>>
>>Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
>
>
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh updated DERBY-1075:
--------------------------------
Attachment: derby-1075-v2.diff
derby-1075-v2.status
Thanks Andreas for pointing out the new case added to phaseTester. I had not noticed the change as it was committed after I uploaded my first patch. I have added this test to UpgradeTester and also updated the master. The new patch is uploaded as 'derby-1075-v2.diff'. With this patch, I have built and run the new upgrade test on WinXP using Sun JDK 1.4.2. Once this patch gets reviewed and committed, it will replace phaseTester.java and runPhases.ksh and we can remove these files.
David, thanks for uploading your classloader work. I extracted the jar file using jar command but I find DerbyLoader.java in unreadable format. I am curious to understand what you have done but do not plan to work on it immediately. So whenever you get time, please check the jar file to see if you are able to read DerbyLoader.java.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371460 ]
Kathey Marsden commented on DERBY-1075:
---------------------------------------
Thanks Deepa
I will try to commit this patch today. I think even if I have comments I will go ahead and commit as it is important to make this available to the community as soon as possible.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Mike Matrigali updated DERBY-1075:
----------------------------------
Component: Test
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371513 ]
Kathey Marsden commented on DERBY-1075:
---------------------------------------
I checked in this patch as it looks like great progress on this issue. I did not review the code change in detail but I tried to run the test and noticed a couple of things.
1) The build does not build the new directory. Probably planned in a later patch but thought I would mention it.
2) The instructions to run the test had the package ommitted. Should be:
ava org.apache.derbyTesting.functionTests.tests.upgradeTests.Upgrade_10_1_10_2 <location of old jars> <location of new jars>
e.g, java org.apache.derbyTesting.functionTests.tests.upgradeTests.Upgrade_10_1_10_2 C:\derby\10.1\lib C:\derby\trunk\lib
3) When I tried to run the test it terminated witha a Table does not exist message. What might I be doing wrong?
START - phase CREATE
END - PASS - phase CREATE
START - phase SOFT UPGRADE
complete caseVersionCheck - passed true
caseReusableRecordIdSequenceNumber - Running compress
SQLException:
SQLSTATE(42X05): Table 'APP.CT1' does not exist.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371406 ]
Andreas Korneliussen commented on DERBY-1075:
---------------------------------------------
Recently it was added a case called caseReusableRecordIdSequenceNumber() to phaseTester.java. It seems like this case is not included in this patch. Would it be ok to add it to the upgrade test as part of this patch ?
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Assigned: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh reassigned DERBY-1075:
-----------------------------------
Assign To: Deepa Remesh
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371722 ]
Knut Anders Hatlen commented on DERBY-1075:
-------------------------------------------
The canon seems to be based on Derby 10.1.2.2. Shouldn't we use an official release (10.1.2.1) instead? If not, where can I find 10.1.2.2?
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371355 ]
Deepa Remesh commented on DERBY-1075:
-------------------------------------
Thanks David for looking at the patch.
The reason I have the call to setContextClassLoader is to ensure that any classes which are used in a particular phase of the test get loaded by the specified class loader. After I saw David's comment, I re-read the javadoc for this and now I am not sure it serves the purpose I just mentioned. To ensure the classes get loaded by a specific class loader, I am explicitly using Class.forName by specifying a class loader (to load TestUtil and metadata classes). Maybe the call to setContextClassLoader is not serving any purpose. I would appreciate any insights into use of setContextClassLoader.
David, I would like to see your example to understand how to use interfaces to achieve the same thing. It would be nice if you can upload the example. Thanks.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh updated DERBY-1075:
--------------------------------
Attachment: loader_v2.java
Attaching a newer version of test program 'loader_v2.java'. I noticed I was creating new classloader for each test instead of re-using the classloader.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371334 ]
David Van Couvering commented on DERBY-1075:
--------------------------------------------
I looked at this patch and it looks *very good*! Thanks, Deepa, for addressing a very important issue and writing code that is very easy to read and follow.
I did have one little eensy weensy comment -- I am not *sure* you need to set the context classloader, but I suspect this may be needed by the underlying classloader stuff in the engine.
Also, if you tire of reflection, there is another way to do this using interfaces that makes writing test code much easier. Basically, you define an interface that is implemented by the class you are trying to work with (e.g. the metadata test class). Then you can cast the class you load with your specialized classloader into the interface you have defined. It's OK that the interface and the implementation are loaded by different classloaders (as long as the interface class is *only* loaded by your default classloader and not by the specialized one, which is generally the case). After that you can invoke methods on the interface using regular, type-checked Java code.
I have some code that shows how this is done sitting in my sandbox for the classloading work I was doing for shared code if you'd like to see an example.
Right now, it's not a lot of reflection, but in case it starts getting a little hairy...
I vote +1 on this patch, but I personally hesitate to commit it without some other folks reviewing it. Deepa, if you don't get any other reviews in the next few days, let me know, and I'll go ahead and commit.
David
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Resolved: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh resolved DERBY-1075:
---------------------------------
Resolution: Fixed
Resolving issue as upgrade test has been converted to a java test.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371362 ]
David Van Couvering commented on DERBY-1075:
--------------------------------------------
This is a very common misunderstanding of setContextClassLoader, and one that has thrown many of us, including myself, for quite a loop. It turns out that setContextClassLoader() is of *absolutely no use* unless someone later on in the same thread decides to grab it using getContextClassLoader() and use it. It appears to be most commonly used by application servers, who want to use a separate classloader for each thread.
That said, it is worth noting that org.apache.derby.impl.services.reflect.ReflectClassesJava2 appears to use getContextClassLoader. It appears to be used to load classes that are not in derby.jar (e.g. application classes), I *think* if the class can't be found by the default classloader. I'm not sure if this is the right thing to do, but this is what it does. You might just try not setting the context classloader and see what happens, but I guess if you want to be safe you might as well go and set it.
But you're right, the way to get a class to use a specific classloader as its *default* classloader (which is *different* from the context classloader) is to use Class.forName() or otherwise explicitly load that class using the classloader you want. Then whenever it does "new" it uses that classloader.
I'll attach the code, once I find it.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh updated DERBY-1075:
--------------------------------
Attachment: loader.java
I have written a small java program 'loader.java' to test that I can load different version of derby classes using a classloader. After loading a particular version of Derby, I get a connection and check the product version in the connection metadata. I found that I can switch between versions without problems. I also checked that the classloader ignores the settings in the class path and uses only what is specified in the program. So all the following commands result in same output:
1. java -classpath . loader C:\deepa\Derby\10.1\classes C:\deepa\Derby\trunk\classes
2. java -classpath .;C:\deepa\Derby\10.1\classes loader C:\deepa\Derby\10.1\classes C:\deepa\Derby\trunk\classes
3. java -classpath .;C:\deepa\Derby\trunk\classes loader C:\deepa\Derby\10.1\classes C:\deepa\Derby\trunk\classes
However, I found I cannot use DriverManager to get a connection. The reason I think is this statement from the javadoc "When the method getConnection is called, the DriverManager will attempt to locate a suitable driver from amongst those loaded at initialization and those loaded explicitly using the same classloader as the current applet or application.". Use of DataSource to get connection works fine. I hope it is okay to proceed by using DataSource. I would appreciate if someone can take a quick look at the attached program and let me know if this is the right direction.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: loader.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Commented: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=comments#action_12371635 ]
Deepa Remesh commented on DERBY-1075:
-------------------------------------
Thanks Kathey. Please see answers for your questions:
1) The build does not build the new directory. Probably planned in a later patch but thought I would mention it.
I do not understand what is different in your environment. For me, the new directory gets built and packaged into derbyTesting.jar (sane build)
2) The instructions to run the test had the package ommitted.
Thanks. I'll change this
3) When I tried to run the test it terminated witha a Table does not exist message. What might I be doing wrong?
Again, not sure what is the problem here. The table you mention is created in the old release and should be present after soft upgrade. Can you post the whole output from the test? I'll take a look.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
Re: [jira] Updated: (DERBY-1075) Combine the script and the test available for upgrade testing into a java test
Posted by Deepa Remesh <dr...@gmail.com>.
On 3/19/06, Bryan Pendleton <bp...@amberpoint.com> wrote:
> Deepa Remesh (JIRA) wrote:
> > It should be possible to add more tests using the jar locations for each old/new release combination to be tested.
> >
> > 2. The new master added 'UpgradeTester.out' is based on phaseTester.out with few diffs in the statements printed out.
> >
> > To run upgrade tests using this class, use the command:
> > java UpgradeTester <location of old jars> <location of new jars> <old major version> <old minor version>
> > e.g, java UpgradeTester C:\derby\10.1\lib C:\derby\trunk\lib 10 1
>
> If we anticipate that we will eventually have several different upgrade
> scenarios and combinations of releases that we desire to support, is it
> worth spending a bit of time now coming up with naming conventions
> for the master files so that it will be easy to tell them apart?
>
> That is, should 'UpgradeTester.out' really be named something like
> 'UpgradeTester_10_1_10_2.out'?
>
Thanks Bryan for looking at this. I have been thinking along the same
lines. Here is what I have been thinking:
* Use the UpgradeTester class as the common class which can be used to
run upgrade test given an old and new release.
* Add new classes for each combination similar to what you suggested:
UpgradeTester_10_1_10_2.
* Remove version specific information from the master file. Do the
version checks in UpgradeTester class itself and sed out any version
information from the output.
* Support testing of upgrade in network client environment.
Thanks,
Deepa
*
Re: [jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by Bryan Pendleton <bp...@amberpoint.com>.
Deepa Remesh (JIRA) wrote:
> It should be possible to add more tests using the jar locations for each old/new release combination to be tested.
>
> 2. The new master added 'UpgradeTester.out' is based on phaseTester.out with few diffs in the statements printed out.
>
> To run upgrade tests using this class, use the command:
> java UpgradeTester <location of old jars> <location of new jars> <old major version> <old minor version>
> e.g, java UpgradeTester C:\derby\10.1\lib C:\derby\trunk\lib 10 1
If we anticipate that we will eventually have several different upgrade
scenarios and combinations of releases that we desire to support, is it
worth spending a bit of time now coming up with naming conventions
for the master files so that it will be easy to tell them apart?
That is, should 'UpgradeTester.out' really be named something like
'UpgradeTester_10_1_10_2.out'?
thanks,
bryan
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh updated DERBY-1075:
--------------------------------
Attachment: derby-1075-patch1-draft.diff
derby-1075-patch1-draft.status
Attaching a draft patch 'derby-1075-patch1-draft.diff'. This patch combines runphases.ksh and phaseTester.java into a single java class 'UpgradeTester'. This patch is only for review and not for commit.
Summary of patch:
1. The new class UpgradeTester does the following:
* Creates two class loaders using the jar locations provided for old and new release
* Switches between these two class loaders to run the different upgrade phases with old or new release.
* Has a main method which takes following inputs: <location of old jars>, <location of new jars>, <old major version>, <old minor version>
This is same as inputs needed by runphases.ksh. Once the previous release jars are available in svn, we can avoid taking command-line inputs and it should be possible to add this as a harness test. It should be possible to add more tests using the jar locations for each old/new release combination to be tested.
2. The new master added 'UpgradeTester.out' is based on phaseTester.out with few diffs in the statements printed out.
To run upgrade tests using this class, use the command:
java UpgradeTester <location of old jars> <location of new jars> <old major version> <old minor version>
e.g, java UpgradeTester C:\derby\10.1\lib C:\derby\trunk\lib 10 1
The test run still has to be compared manually to the out file 'UpgradeTester.out' and will show many diffs. DERBY-1076 is open to resolve these diffs.
I am continuing with few minor changes on the patch and will upload a newer version when done. In the meantime, I would appreciate any feedback on the patch. Specifically, I would like to know if I have missed anything when converting the test.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Updated: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh updated DERBY-1075:
--------------------------------
Attachment: derby-1075-v1.diff
derby-1075-v1.status
Attaching a patch 'derby-1075-v1.diff'. This patch is based on the draft patch with some additional changes.
Summary of patch:
1. Creates a class UpgradeTester which does the following:
* Creates two class loaders using the jar locations provided for old and new release
* Switches between these two class loaders to run the different upgrade phases with old or new release.
* This class can be used to write tests for upgrades from different releases.
2. Adds a new test Upgrade_10_1_10_2 which uses UpgradeTester to test upgrade from 10.1 to 10.2. This test has not been added to any suite. Till the jars from previous release are available in svn, the test has to be run manually using the command:
java Upgrade_10_1_10_2 <location of old jars> <location of new jars>
e.g, java Upgrade_10_1_10_2 C:\derby\10.1\lib C:\derby\trunk\lib
Also, there are some issues in running the test using the harness because of use of security manager. These are mentioned in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. Any suggestions to resolve these are welcome. I am planning to open separate sub-task for making this test run with a security manager.
3. Creates a new package upgradeTests under org.apache.derbyTesting.functionTests.tests. This package is for UpgradeTester class and the individual upgrade tests.
4. Adds a master 'Upgrade_10_1_10_2.out'. I have tried to reduce the diffs by doing version check in the code and removing reference to local machine paths. Still, there are few more diffs. I am planning to look at these once this patch is reviewed/committed.
This patch only adds new files. I verified that build is successful and I can run the new test. I would appreciate if someone can take a look at this patch and review/commit it.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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
[jira] Closed: (DERBY-1075) Combine the script and the test
available for upgrade testing into a java test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh closed DERBY-1075:
-------------------------------
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: classloader.jar, derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, derby-1075-v2.diff, derby-1075-v2.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.
--
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