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 "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2005/11/08 05:45:20 UTC
[jira] Created: (DERBY-689) Various improvements to compatibility test.
Various improvements to compatibility test.
-------------------------------------------
Key: DERBY-689
URL: http://issues.apache.org/jira/browse/DERBY-689
Project: Derby
Type: Improvement
Reporter: Rick Hillegas
Improve compatibility test as various reviewers requested.
--
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-689) Various improvements to compatibility test.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas reassigned DERBY-689:
-----------------------------------
Assign To: Rick Hillegas
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: http://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Type: Improvement
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
>
> Improve compatibility test as various reviewers requested.
--
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-689) Various improvements to compatibility
test.
Posted by David Van Couvering <Da...@Sun.COM>.
Hi, Rick, I'll try to get to this today.
David
Rick Hillegas (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>
> Rick Hillegas updated DERBY-689:
> --------------------------------
>
> Attachment: bug689_2.diff
>
> bug689_2.diff further improves this suite by adding a target for running just one combination of client/clientVM/server/serverVM. The target is called oneCombination and it is explained by -projecthelp. Since this patch does not touch any code involved in the product or the regression tests, it should be safe to check in as is:
>
> M java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\oneCombo.properties
>
>
>>Various improvements to compatibility test.
>>-------------------------------------------
>>
>> Key: DERBY-689
>> URL: http://issues.apache.org/jira/browse/DERBY-689
>> Project: Derby
>> Type: Improvement
>> Reporter: Rick Hillegas
>> Assignee: Rick Hillegas
>> Attachments: bug689.diff, bug689_2.diff
>>
>>Improve compatibility test as various reviewers requested.
>
>
[jira] Updated: (DERBY-689) Various improvements to compatibility test.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas updated DERBY-689:
--------------------------------
Attachment: bug689_2.diff
bug689_2.diff further improves this suite by adding a target for running just one combination of client/clientVM/server/serverVM. The target is called oneCombination and it is explained by -projecthelp. Since this patch does not touch any code involved in the product or the regression tests, it should be safe to check in as is:
M java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\oneCombo.properties
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: http://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Type: Improvement
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: bug689.diff, bug689_2.diff
>
> Improve compatibility test as various reviewers requested.
--
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-689) Various improvements to compatibility
test.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-689:
--------------------------------
Fix Version/s: 10.2.1.6
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: https://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Rick Hillegas
> Assigned To: Rick Hillegas
> Fix For: 10.2.1.6
>
> Attachments: bug689.diff, bug689_2.diff
>
>
> Improve compatibility test as various reviewers requested.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-689) Various improvements to compatibility
test.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Kathey Marsden updated DERBY-689:
---------------------------------
Component: Test
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: http://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Type: Improvement
> Components: Test
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: bug689.diff, bug689_2.diff
>
> Improve compatibility test as various reviewers requested.
--
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-689) Various improvements to compatibility test.
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
David Van Couvering resolved DERBY-689:
---------------------------------------
Resolution: Fixed
Checked in the second patch
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: http://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Type: Improvement
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: bug689.diff, bug689_2.diff
>
> Improve compatibility test as various reviewers requested.
--
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: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
I'm happy, as long as there are plans to make this optional in the future.
David
Rick Hillegas wrote:
> Hi Dan,
>
> I think that I may be talking past you and David. Some confusion may be
> caused by the fact that the compatibility test runs under two harnesses:
>
> 1) The derbyall harness runs one combination of the test. This
> combination is ( Client = mainline DerbyClient, ClientVM = user's
> default, Server = mainline DerbyServer, ServerVM = user's default ).
> DB2JCC is not required for this.
>
> 2) The compatibility suite harness runs all combinations of the test.
> Currently this only happens when someone bothers to setup the
> environment and run the suite. However, it's my hope that the full suite
> will be run as part of some automated process on a nightly/weekly basis
> and before vetting a release candidate. DB2JCC is part of the required
> environment for this full suite. The required environment also includes
> three vms (jdk1.3, jdk1.4, and jdk1.5) and four Derby releases (10.0,
> 10.1.1.0, 10.1.2.0, mainline jars).
>
> The suite harness is not configurable currently. Right now you have to
> run all combinations and therefore have a complete environment. As part
> of some future submission, I intend to put in logic to make it possible
> to run just one combination under the suite harness. When I do that, I
> can make extraneous parts of the environment (such as DB2JCC) optional.
>
> I hope this clarifies the situation.
>
> Cheers,
> -Rick
>
> Daniel John Debrunner wrote:
>
>> Rick Hillegas wrote:
>>
>>
>>
>>
>>> DB2JCC is included because some Derby customers use it and I thought the
>>> community would be interested in tracking its compatibility issues. For
>>> instance, we might want to understand issues which customers will face
>>> if they migrate off DB2JCC onto DerbyClient 10.2. Based on previous
>>> email threads, I could see these compatibility issues gating the
>>> acceptance of proposals or releases by some of our committers.
>>>
>>
>>
>> That's great to include tests/framework for JCC.
>>
>> The question is can it be optional, or must I download JCC to run these
>> tests with combinations that do not include JCC?
>>
>> People who want to test JCC should be able to, those that don't
>> shouldn't be required to download JCC.
>>
>> Thanks,
>> Dan.
>>
>>
>>
>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Dan,
I think that I may be talking past you and David. Some confusion may be
caused by the fact that the compatibility test runs under two harnesses:
1) The derbyall harness runs one combination of the test. This
combination is ( Client = mainline DerbyClient, ClientVM = user's
default, Server = mainline DerbyServer, ServerVM = user's default ).
DB2JCC is not required for this.
2) The compatibility suite harness runs all combinations of the test.
Currently this only happens when someone bothers to setup the
environment and run the suite. However, it's my hope that the full suite
will be run as part of some automated process on a nightly/weekly basis
and before vetting a release candidate. DB2JCC is part of the required
environment for this full suite. The required environment also includes
three vms (jdk1.3, jdk1.4, and jdk1.5) and four Derby releases (10.0,
10.1.1.0, 10.1.2.0, mainline jars).
The suite harness is not configurable currently. Right now you have to
run all combinations and therefore have a complete environment. As part
of some future submission, I intend to put in logic to make it possible
to run just one combination under the suite harness. When I do that, I
can make extraneous parts of the environment (such as DB2JCC) optional.
I hope this clarifies the situation.
Cheers,
-Rick
Daniel John Debrunner wrote:
>Rick Hillegas wrote:
>
>
>
>
>>DB2JCC is included because some Derby customers use it and I thought the
>>community would be interested in tracking its compatibility issues. For
>>instance, we might want to understand issues which customers will face
>>if they migrate off DB2JCC onto DerbyClient 10.2. Based on previous
>>email threads, I could see these compatibility issues gating the
>>acceptance of proposals or releases by some of our committers.
>>
>>
>
>That's great to include tests/framework for JCC.
>
>The question is can it be optional, or must I download JCC to run these
>tests with combinations that do not include JCC?
>
>People who want to test JCC should be able to, those that don't
>shouldn't be required to download JCC.
>
>Thanks,
>Dan.
>
>
>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to compatibility test.
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 9, 2005, at 10:23 AM, David W. Van Couvering wrote:
> I also don't think a release manager should be *required* to run
> compatibility tests for JCC (although most probably will). If a
> particular release manager for a particular release doesn't care,
> it seems they shouldn't have to.
I don't think a release manager is required to run any tests, period.
A responsible release manager will surely run some testing to make
sure that they're not putting forward a broken build, but even that
is not a requirement. Testing is done by the community, and the
feedback from their testing is the basis for their plus or minus vote
for the release. It is up to the members of the community interested
in compatibility testing to provide those results for any proposed
release. There is too much testing for a release manager to do all of
it, so the community distributes the load, and voting provides the
feedback mechanism.
> That said, I suspect those committers who do care will probably run
> JCC compatibility tests and vote -1 on a release *if* JCC doesn't
> work because the currently implementation of Derby is not compliant
> with the DRDA spec.
Replace 'committers' with 'contributors', and this line of reasoning
applies to all testing done w/r/t a release, not just JCC-related
testing.
andrew
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Yes, that was my point, it should be optional, and it's not documented
that way now. JCC testing should be provided as a nice-to-have feature,
not as a required part of releasing Derby.
I also don't think a release manager should be *required* to run
compatibility tests for JCC (although most probably will). If a
particular release manager for a particular release doesn't care, it
seems they shouldn't have to.
That said, I suspect those committers who do care will probably run JCC
compatibility tests and vote -1 on a release *if* JCC doesn't work
because the currently implementation of Derby is not compliant with the
DRDA spec.
David
Daniel John Debrunner wrote:
> Rick Hillegas wrote:
>
>
>
>>DB2JCC is included because some Derby customers use it and I thought the
>>community would be interested in tracking its compatibility issues. For
>>instance, we might want to understand issues which customers will face
>>if they migrate off DB2JCC onto DerbyClient 10.2. Based on previous
>>email threads, I could see these compatibility issues gating the
>>acceptance of proposals or releases by some of our committers.
>
>
> That's great to include tests/framework for JCC.
>
> The question is can it be optional, or must I download JCC to run these
> tests with combinations that do not include JCC?
>
> People who want to test JCC should be able to, those that don't
> shouldn't be required to download JCC.
>
> Thanks,
> Dan.
>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements
to compatibility test.
Posted by Daniel John Debrunner <dj...@debrunners.com>.
Rick Hillegas wrote:
>
> DB2JCC is included because some Derby customers use it and I thought the
> community would be interested in tracking its compatibility issues. For
> instance, we might want to understand issues which customers will face
> if they migrate off DB2JCC onto DerbyClient 10.2. Based on previous
> email threads, I could see these compatibility issues gating the
> acceptance of proposals or releases by some of our committers.
That's great to include tests/framework for JCC.
The question is can it be optional, or must I download JCC to run these
tests with combinations that do not include JCC?
People who want to test JCC should be able to, those that don't
shouldn't be required to download JCC.
Thanks,
Dan.
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi David,
By "full set of combinations" I mean all values of ( Client, ClientVM,
Server, ServerVM ) where
Client - ranges over all clients we have supported: DB2JCC, DerbyClient
10.1.1.0, DerbyClient 10.1.2.0, DerbyClient mainline (10.2)
ClientVM - ranges over all client VMs we have supported: jdk1.3, jdk1.4,
jdk1.5
Server - ranges over all servers we have supported: DerbyServer 10.0,
DerbyServer 10.1.1.0, DerbyServer 10.1.2.0, DerbyServer mainline (10.2)
ServerVM - ranges over all server VMs we have supported: jdk1.3, jdk1.4,
jdk1.5
DB2JCC is included because some Derby customers use it and I thought the
community would be interested in tracking its compatibility issues. For
instance, we might want to understand issues which customers will face
if they migrate off DB2JCC onto DerbyClient 10.2. Based on previous
email threads, I could see these compatibility issues gating the
acceptance of proposals or releases by some of our committers.
It's just a tool. Right now, a very limited too: I've only logged one
minor incompatibility bug based on this test. As we add more test cases,
we will discover more incompatibilities. Some of these incompatibilities
will be minor and some will be showstoppers.
Do you not want to track incompatibility issues with DB2JCC as part of
running this test suite nightly/weekly/per-release?
-Rick
David W. Van Couvering wrote:
>
>
> Rick Hillegas wrote:
>
>> Hi David,
>>
>> Thanks for this improvement.
>>
>> Right now, the DB2 JCC libraries are required for running the full
>> set of combinations.
>
>
> I'm not sure what you mean here. The full set of combinations of
> what? Why is it required?
>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Rick Hillegas wrote:
> Hi David,
>
> Thanks for this improvement.
>
> Right now, the DB2 JCC libraries are required for running the full set
> of combinations.
I'm not sure what you mean here. The full set of combinations of what?
Why is it required?
Thanks,
David
I don't understand Derby's long term relationship with
> this code. As we add new JDBC support (e.g., JDBC 4.0), we have no
> control over the behavior of this client. Do we expect customers to
> migrate onto Derby's client as of 10.1? I'm not aware of any discussions
> about either continuing or sunsetting support for DB2 JCC.
>
> Regards,
> -Rick
>
> David W. Van Couvering wrote:
>
>> Hi, Rick. I've moved the compatibility test over to derbynetclient,
>> as we agreed.
>>
>> I noticed in the testScript.xml for the compatibility tests that you
>> are asking for the location of the DB2 JCC libraries. Is that required
>> or optional for running compatibility tests?
>>
>> I guess this asks the broader question of: are we required to
>> guarantee backward compatibility with the DB2 JDBC driver as part of a
>> release of Derby?
>>
>> Thanks,
>>
>> David
>>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Sounds like we're in violent agreement :)
David
Daniel John Debrunner wrote:
> David W. Van Couvering wrote:
>
>
>>- I don't think we need to do anything extreme like yanking the support
>>for JCC out of the harness, I think that would be somewhat silly and
>>unhelpful.
>
>
> Not sure why we would ever do anything like that. If someone contributed
> changes to the harness that, say, made it easy to run hibernate based
> tests that would be great. Adding functionality to the harness (or
> elsewhere) to allow improved testing should be encouraged.
>
> Of course you would probably be insane to attempt improving the current
> harness instead of starting afresh with JUnit tests. :-) But the
> principle still stands.
>
> Dan.
>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements
to compatibility test.
Posted by Daniel John Debrunner <dj...@debrunners.com>.
David W. Van Couvering wrote:
> - I don't think we need to do anything extreme like yanking the support
> for JCC out of the harness, I think that would be somewhat silly and
> unhelpful.
Not sure why we would ever do anything like that. If someone contributed
changes to the harness that, say, made it easy to run hibernate based
tests that would be great. Adding functionality to the harness (or
elsewhere) to allow improved testing should be encouraged.
Of course you would probably be insane to attempt improving the current
harness instead of starting afresh with JUnit tests. :-) But the
principle still stands.
Dan.
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Hi, Dan, thanks for your clarifications and the overall approach seems
reasonable.
The one thing I think is confusing and perhaps misleading is that the
JCC tests (for historical reasons I am assuming, because we didn't used
to have our own JDBC driver) are pretty intermingled with the main Derby
testing infrastructure: with the Derby test harness, the Derby testing
infrastructure (e.g. the suites), and the Derby testing documentation.
It would help a LOT if we were more clear about JCC being a consumer of
Derby as much as (as you say) Hibernate, JDO, etc. I'm not sure what
this would look like, here are some quick brainstorms:
- Cleaning up the testing docs as much as possible to make this
distinction clear (I have done a bit of this already).
- Maybe putting the JCC-specific tests in a separate directory like we
have done for the JUnit tests
- Taking JCC tests out of derbyall and making JCC tests an opt-in part
of the gate to checkin rather than an opt-out (e.g. those whose itch it
is to run JCC tests can explicitly do so).
- I don't think we need to do anything extreme like yanking the support
for JCC out of the harness, I think that would be somewhat silly and
unhelpful.
If there is general agreement that there is nothing wrong with making
this distinction more clear (e.g. it doesn't break existing
functionality, doesn't degrade the quality of Derby, and is not against
the charter of Derby), then it seems to me that those who have the itch
to make these types of clarifications should feel free to do so.
Thanks,
David
Daniel John Debrunner wrote:
> Rick Hillegas wrote:
>
>
>>Hi David,
>>
>>Thanks for this improvement.
>>
>>Right now, the DB2 JCC libraries are required for running the full set
>>of combinations.
>
>
> Should the DB2 JCC libraries be required to run Derby's tests?
> The suite derbyall skips the JCC tests (derbynetmats) if JCC is not in
> the classpath.
>
>
>>I don't understand Derby's long term relationship with
>>this code.
>
>
> It's actually very simple. DB2 JCC should be treated like any other
> program that works with Derby, say Hibernate, Apache James, JDO, IBM
> WAS, Cheese Lab etc.
>
> Some aspects of DB2 JCC that maybe make it look different are:
>
> - it uses the socket based api to Derby defined in terms of DRDA.
> - tests have been contributed that test DB2 JCC and Derby.
>
> But, I don't believe they give it any special status compared to other uses.
>
>
>>As we add new JDBC support (e.g., JDBC 4.0), we have no
>>control over the behavior of this client.
>
>
> Not sure what point you are trying to make here. The DBC JCC client
> supports JDBC 3.0 and works today, if Derby has added JDBC 4.0 to its
> clients, how does that affect an independent client?
>
>
>>Do we expect customers to
>>migrate onto Derby's client as of 10.1?
>
>
> Not sure we "expect" anything, people use what they want.
>
>
>>I'm not aware of any discussions
>>about either continuing or sunsetting support for DB2 JCC.
>
>
> It's really about code contributions.
>
> - Any submission (or commit) that breaks existing functionality/api's
> has the potential to be vetoed.
>
> - A submission (or commit) that follows the specs, does not change the
> api, but breaks some specific use of that api, then really it's the
> problem of that use to resolve it. The actual case may determine how we
> treat that submission in terms of commiting it and/or trying to resolve it.
>
> I guess its also about that itch, if people have the itch to continue
> supporting JCC (or anything else) then they will put effort into it. The
> only decision point comes if that effort is in some way preventing some
> progress on something else, someone else's itch. Then neither is more
> important than the other, it's up to the community to discuss and decide
> the direction or solution.
>
> Dan.
>
>
Re: DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements
to compatibility test.
Posted by Daniel John Debrunner <dj...@debrunners.com>.
Rick Hillegas wrote:
> Hi David,
>
> Thanks for this improvement.
>
> Right now, the DB2 JCC libraries are required for running the full set
> of combinations.
Should the DB2 JCC libraries be required to run Derby's tests?
The suite derbyall skips the JCC tests (derbynetmats) if JCC is not in
the classpath.
> I don't understand Derby's long term relationship with
> this code.
It's actually very simple. DB2 JCC should be treated like any other
program that works with Derby, say Hibernate, Apache James, JDO, IBM
WAS, Cheese Lab etc.
Some aspects of DB2 JCC that maybe make it look different are:
- it uses the socket based api to Derby defined in terms of DRDA.
- tests have been contributed that test DB2 JCC and Derby.
But, I don't believe they give it any special status compared to other uses.
> As we add new JDBC support (e.g., JDBC 4.0), we have no
> control over the behavior of this client.
Not sure what point you are trying to make here. The DBC JCC client
supports JDBC 3.0 and works today, if Derby has added JDBC 4.0 to its
clients, how does that affect an independent client?
> Do we expect customers to
> migrate onto Derby's client as of 10.1?
Not sure we "expect" anything, people use what they want.
> I'm not aware of any discussions
> about either continuing or sunsetting support for DB2 JCC.
It's really about code contributions.
- Any submission (or commit) that breaks existing functionality/api's
has the potential to be vetoed.
- A submission (or commit) that follows the specs, does not change the
api, but breaks some specific use of that api, then really it's the
problem of that use to resolve it. The actual case may determine how we
treat that submission in terms of commiting it and/or trying to resolve it.
I guess its also about that itch, if people have the itch to continue
supporting JCC (or anything else) then they will put effort into it. The
only decision point comes if that effort is in some way preventing some
progress on something else, someone else's itch. Then neither is more
important than the other, it's up to the community to discuss and decide
the direction or solution.
Dan.
DB2JCC, was: [jira] Updated: (DERBY-689) Various improvements to
compatibility test.
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi David,
Thanks for this improvement.
Right now, the DB2 JCC libraries are required for running the full set
of combinations. I don't understand Derby's long term relationship with
this code. As we add new JDBC support (e.g., JDBC 4.0), we have no
control over the behavior of this client. Do we expect customers to
migrate onto Derby's client as of 10.1? I'm not aware of any discussions
about either continuing or sunsetting support for DB2 JCC.
Regards,
-Rick
David W. Van Couvering wrote:
> Hi, Rick. I've moved the compatibility test over to derbynetclient,
> as we agreed.
>
> I noticed in the testScript.xml for the compatibility tests that you
> are asking for the location of the DB2 JCC libraries. Is that required
> or optional for running compatibility tests?
>
> I guess this asks the broader question of: are we required to
> guarantee backward compatibility with the DB2 JDBC driver as part of a
> release of Derby?
>
> Thanks,
>
> David
>
> Rick Hillegas (JIRA) wrote:
>
>> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>>
>> Rick Hillegas updated DERBY-689:
>> --------------------------------
>>
>> Attachment: bug689.diff
>>
>> Various improvements to compatibility test:
>>
>> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as
>> Myrna and John requested.
>>
>> 2) Made the test harness sanity check the classpath as David requested.
>>
>> 3) Abstracted a CompatibilitySuite out of the original test to make
>> it easier to add more test classes, as Francois requested.
>>
>> 4) Added combinations for the 10.1.2.0 client and server
>>
>> 5) The derbyall diff tool was enhanced to fabricate an empty canon
>> file if one doesn't exist in the codeline. This eliminates the need
>> to create empty canons for JUnit tests.
>>
>> The svn status for this patch follows:
>>
>> M java\testing\README.htm
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
>>
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
>>
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
>>
>> M java\testing\build.xml
>>
>> Note that functionTests/tests/compatibility was svn moved to
>> functionTests/tests/junitTests/compatibility and the
>> CompatibiltiyTest itself was svn moved to
>> functionTests/tests/junitTests/derbynet.
>>
>> The compatibility test suite runs cleanly on my machine and so does
>> derbyall.
>>
>>
>>> Various improvements to compatibility test.
>>> -------------------------------------------
>>>
>>> Key: DERBY-689
>>> URL: http://issues.apache.org/jira/browse/DERBY-689
>>> Project: Derby
>>> Type: Improvement
>>> Reporter: Rick Hillegas
>>> Assignee: Rick Hillegas
>>> Attachments: bug689.diff
>>>
>>> Improve compatibility test as various reviewers requested.
>>
>>
>>
Re: [jira] Updated: (DERBY-689) Various improvements to compatibility
test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Hi, Rick. I've moved the compatibility test over to derbynetclient, as
we agreed.
I noticed in the testScript.xml for the compatibility tests that you
are asking for the location of the DB2 JCC libraries. Is that required
or optional for running compatibility tests?
I guess this asks the broader question of: are we required to guarantee
backward compatibility with the DB2 JDBC driver as part of a release of
Derby?
Thanks,
David
Rick Hillegas (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>
> Rick Hillegas updated DERBY-689:
> --------------------------------
>
> Attachment: bug689.diff
>
> Various improvements to compatibility test:
>
> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as Myrna and John requested.
>
> 2) Made the test harness sanity check the classpath as David requested.
>
> 3) Abstracted a CompatibilitySuite out of the original test to make it easier to add more test classes, as Francois requested.
>
> 4) Added combinations for the 10.1.2.0 client and server
>
> 5) The derbyall diff tool was enhanced to fabricate an empty canon file if one doesn't exist in the codeline. This eliminates the need to create empty canons for JUnit tests.
>
> The svn status for this patch follows:
>
> M java\testing\README.htm
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
> D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
> M java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
> M java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
> D java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
> M java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
> M java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
> M java\testing\build.xml
>
> Note that functionTests/tests/compatibility was svn moved to functionTests/tests/junitTests/compatibility and the CompatibiltiyTest itself was svn moved to functionTests/tests/junitTests/derbynet.
>
> The compatibility test suite runs cleanly on my machine and so does derbyall.
>
>
>>Various improvements to compatibility test.
>>-------------------------------------------
>>
>> Key: DERBY-689
>> URL: http://issues.apache.org/jira/browse/DERBY-689
>> Project: Derby
>> Type: Improvement
>> Reporter: Rick Hillegas
>> Assignee: Rick Hillegas
>> Attachments: bug689.diff
>>
>>Improve compatibility test as various reviewers requested.
>
>
Re: [jira] Updated: (DERBY-689) Various improvements to compatibility
test.
Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks, David.
David W. Van Couvering wrote:
> Looks good. The compatiblity tests and derbynetclientmats run
> successfully. I committed this change, revision 332090.
>
> I am unable to update the bug as fixed as Jira appears to be down
> right now. I'll notify infra if this continues to be an issue.
>
> David
>
> Sending java\testing\README.htm
> Sending java\testing\build.xml
> Sending java\testing\org\apache\derbyTesting\functionTests\harness\FileCo
> mpare.java
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\master\Compati
> bilityTest.out
> Sending java\testing\org\apache\derbyTesting\functionTests\suites\derbyne
> tclientmats.runall
> Sending java\testing\org\apache\derbyTesting\functionTests\suites\derbyne
> tmats.runall
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\compatib
> ility\JDBCDriverTest.java
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\compatib
> ility\Pinger.java
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\compatib
> ility\README.html
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\compatib
> ility\build.xml
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\compatib
> ility\testScript.xml
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
> CompatibilityTest.java
> Deleting
> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
> CompatibilityTest_app.properties
> Sending java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
> copyfiles.ant
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility\CompatibilitySuite.java
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility\JDBCDriverTest.java
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility\Pinger.java
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility\README.html
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility\build.xml
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\compatibility\testScript.xml
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\derbyNet
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\derbyNet\CompatibilityTest.java
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\derbyNet\CompatibilityTest_app.properties
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\derbyNet\build.xml
> Adding java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
> ts\derbyNet\copyfiles.ant
> Sending java\testing\org\apache\derbyTesting\functionTests\tests\tools\bu
> ild.xml
> Sending java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUni
> tTest.java
> Transmitting file data ..................
> Committed revision 332090.
>
> Rick Hillegas (JIRA) wrote:
>
>> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>>
>> Rick Hillegas updated DERBY-689:
>> --------------------------------
>>
>> Attachment: bug689.diff
>>
>> Various improvements to compatibility test:
>>
>> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as
>> Myrna and John requested.
>>
>> 2) Made the test harness sanity check the classpath as David requested.
>>
>> 3) Abstracted a CompatibilitySuite out of the original test to make
>> it easier to add more test classes, as Francois requested.
>>
>> 4) Added combinations for the 10.1.2.0 client and server
>>
>> 5) The derbyall diff tool was enhanced to fabricate an empty canon
>> file if one doesn't exist in the codeline. This eliminates the need
>> to create empty canons for JUnit tests.
>>
>> The svn status for this patch follows:
>>
>> M java\testing\README.htm
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
>>
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
>>
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
>>
>> M java\testing\build.xml
>>
>> Note that functionTests/tests/compatibility was svn moved to
>> functionTests/tests/junitTests/compatibility and the
>> CompatibiltiyTest itself was svn moved to
>> functionTests/tests/junitTests/derbynet.
>>
>> The compatibility test suite runs cleanly on my machine and so does
>> derbyall.
>>
>>
>>> Various improvements to compatibility test.
>>> -------------------------------------------
>>>
>>> Key: DERBY-689
>>> URL: http://issues.apache.org/jira/browse/DERBY-689
>>> Project: Derby
>>> Type: Improvement
>>> Reporter: Rick Hillegas
>>> Assignee: Rick Hillegas
>>> Attachments: bug689.diff
>>>
>>> Improve compatibility test as various reviewers requested.
>>
>>
>>
Re: [jira] Updated: (DERBY-689) Various improvements to compatibility
test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Looks good. The compatiblity tests and derbynetclientmats run
successfully. I committed this change, revision 332090.
I am unable to update the bug as fixed as Jira appears to be down right
now. I'll notify infra if this continues to be an issue.
David
Sending java\testing\README.htm
Sending java\testing\build.xml
Sending
java\testing\org\apache\derbyTesting\functionTests\harness\FileCo
mpare.java
Deleting
java\testing\org\apache\derbyTesting\functionTests\master\Compati
bilityTest.out
Sending
java\testing\org\apache\derbyTesting\functionTests\suites\derbyne
tclientmats.runall
Sending
java\testing\org\apache\derbyTesting\functionTests\suites\derbyne
tmats.runall
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\compatib
ility\JDBCDriverTest.java
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\compatib
ility\Pinger.java
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\compatib
ility\README.html
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\compatib
ility\build.xml
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\compatib
ility\testScript.xml
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
CompatibilityTest.java
Deleting
java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
CompatibilityTest_app.properties
Sending
java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
copyfiles.ant
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility\CompatibilitySuite.java
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility\JDBCDriverTest.java
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility\Pinger.java
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility\README.html
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility\build.xml
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\compatibility\testScript.xml
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\derbyNet
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\derbyNet\CompatibilityTest.java
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\derbyNet\CompatibilityTest_app.properties
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\derbyNet\build.xml
Adding
java\testing\org\apache\derbyTesting\functionTests\tests\junitTes
ts\derbyNet\copyfiles.ant
Sending
java\testing\org\apache\derbyTesting\functionTests\tests\tools\bu
ild.xml
Sending
java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUni
tTest.java
Transmitting file data ..................
Committed revision 332090.
Rick Hillegas (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>
> Rick Hillegas updated DERBY-689:
> --------------------------------
>
> Attachment: bug689.diff
>
> Various improvements to compatibility test:
>
> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as Myrna and John requested.
>
> 2) Made the test harness sanity check the classpath as David requested.
>
> 3) Abstracted a CompatibilitySuite out of the original test to make it easier to add more test classes, as Francois requested.
>
> 4) Added combinations for the 10.1.2.0 client and server
>
> 5) The derbyall diff tool was enhanced to fabricate an empty canon file if one doesn't exist in the codeline. This eliminates the need to create empty canons for JUnit tests.
>
> The svn status for this patch follows:
>
> M java\testing\README.htm
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
> D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
> M java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
> M java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
> D java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
> M java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
> M java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
> M java\testing\build.xml
>
> Note that functionTests/tests/compatibility was svn moved to functionTests/tests/junitTests/compatibility and the CompatibiltiyTest itself was svn moved to functionTests/tests/junitTests/derbynet.
>
> The compatibility test suite runs cleanly on my machine and so does derbyall.
>
>
>>Various improvements to compatibility test.
>>-------------------------------------------
>>
>> Key: DERBY-689
>> URL: http://issues.apache.org/jira/browse/DERBY-689
>> Project: Derby
>> Type: Improvement
>> Reporter: Rick Hillegas
>> Assignee: Rick Hillegas
>> Attachments: bug689.diff
>>
>>Improve compatibility test as various reviewers requested.
>
>
Re: [jira] Updated: (DERBY-689) Various improvements to compatibility test.
Posted by Myrna van Lunteren <m....@gmail.com>.
Actually, I think that is an important point, thx David...
I've been surprised about this test failing in a configuration with only
db2jcc, i.e. no derby client, when there is never any reference to jcc in
this test.
I think this test should indeed be *only* run with
framework=DerbyNetClient, and thus, it should be listed only in
derbynetclientmats.runall.
derbynetmats should list those tests that run with both frameworks.
Although we cannot require everyone to run tests with jcc, we do still need
to support that framework - there are existing customers.
Myrna
On 11/8/05, Rick Hillegas <Ri...@sun.com> wrote:
>
> Hi David,
>
> Please feel free to move the compatibility test to the framework you
> prefer.
>
> I apologize for the churn caused by moving files around. I second your
> appeal for better patch technology.
>
> -Rick
>
> David W. Van Couvering wrote:
>
> > Hi, Rick. I have (finally) been able to apply this patch. My
> > goodness, moving files/directories is a bit if a nightmare with svn
> > diff / patch. Did someone say there is a better patch program that
> > can handle this?
> >
> > Is there a reason you are running the compatibility tests in
> > derbynetmats suite? Shouldn't this be in derbynetclientmats?
> > derbynetmats runs with the DB2 JDBC driver, which although interesting
> > seems less important than the Derby JDBC driver.
> >
> > Thanks,
> >
> > David
> >
> >
> > Rick Hillegas (JIRA) wrote:
> >
> >> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
> >>
> >> Rick Hillegas updated DERBY-689:
> >> --------------------------------
> >>
> >> Attachment: bug689.diff
> >>
> >> Various improvements to compatibility test:
> >>
> >> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as
> >> Myrna and John requested.
> >>
> >> 2) Made the test harness sanity check the classpath as David requested.
> >>
> >> 3) Abstracted a CompatibilitySuite out of the original test to make
> >> it easier to add more test classes, as Francois requested.
> >>
> >> 4) Added combinations for the 10.1.2.0 <http://10.1.2.0> client and
> server
> >>
> >> 5) The derbyall diff tool was enhanced to fabricate an empty canon
> >> file if one doesn't exist in the codeline. This eliminates the need
> >> to create empty canons for JUnit tests.
> >>
> >> The svn status for this patch follows:
> >>
> >> M java\testing\README.htm
> >> D
> >> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
> >>
> >> M
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
> >>
> >> A
> >> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
> >> A +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
> >>
> >> M +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
> >>
> >> M +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
> >>
> >> A
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
> >>
> >> M +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
> >>
> >> M +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
> >>
> >> M +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
> >>
> >> A
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
> >>
> >> A +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
> >>
> >> A +
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
> >>
> >> A
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
> >>
> >> A
> >>
> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
> >>
> >> M
> >>
> java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
> >>
> >> D
> >>
> java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
> >>
> >> M
> >>
> java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
> >>
> >> M
> >>
> java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
> >>
> >> M java\testing\build.xml
> >>
> >> Note that functionTests/tests/compatibility was svn moved to
> >> functionTests/tests/junitTests/compatibility and the
> >> CompatibiltiyTest itself was svn moved to
> >> functionTests/tests/junitTests/derbynet.
> >>
> >> The compatibility test suite runs cleanly on my machine and so does
> >> derbyall.
> >>
> >>
> >>> Various improvements to compatibility test.
> >>> -------------------------------------------
> >>>
> >>> Key: DERBY-689
> >>> URL: http://issues.apache.org/jira/browse/DERBY-689
> >>> Project: Derby
> >>> Type: Improvement
> >>> Reporter: Rick Hillegas
> >>> Assignee: Rick Hillegas
> >>> Attachments: bug689.diff
> >>>
> >>> Improve compatibility test as various reviewers requested.
> >>
> >>
> >>
>
>
Re: [jira] Updated: (DERBY-689) Various improvements to compatibility
test.
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi David,
Please feel free to move the compatibility test to the framework you prefer.
I apologize for the churn caused by moving files around. I second your
appeal for better patch technology.
-Rick
David W. Van Couvering wrote:
> Hi, Rick. I have (finally) been able to apply this patch. My
> goodness, moving files/directories is a bit if a nightmare with svn
> diff / patch. Did someone say there is a better patch program that
> can handle this?
>
> Is there a reason you are running the compatibility tests in
> derbynetmats suite? Shouldn't this be in derbynetclientmats?
> derbynetmats runs with the DB2 JDBC driver, which although interesting
> seems less important than the Derby JDBC driver.
>
> Thanks,
>
> David
>
>
> Rick Hillegas (JIRA) wrote:
>
>> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>>
>> Rick Hillegas updated DERBY-689:
>> --------------------------------
>>
>> Attachment: bug689.diff
>>
>> Various improvements to compatibility test:
>>
>> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as
>> Myrna and John requested.
>>
>> 2) Made the test harness sanity check the classpath as David requested.
>>
>> 3) Abstracted a CompatibilitySuite out of the original test to make
>> it easier to add more test classes, as Francois requested.
>>
>> 4) Added combinations for the 10.1.2.0 client and server
>>
>> 5) The derbyall diff tool was enhanced to fabricate an empty canon
>> file if one doesn't exist in the codeline. This eliminates the need
>> to create empty canons for JUnit tests.
>>
>> The svn status for this patch follows:
>>
>> M java\testing\README.htm
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
>>
>> M +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
>>
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
>>
>> A +
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
>>
>> A
>> java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
>>
>> D
>> java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
>>
>> M
>> java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
>>
>> M java\testing\build.xml
>>
>> Note that functionTests/tests/compatibility was svn moved to
>> functionTests/tests/junitTests/compatibility and the
>> CompatibiltiyTest itself was svn moved to
>> functionTests/tests/junitTests/derbynet.
>>
>> The compatibility test suite runs cleanly on my machine and so does
>> derbyall.
>>
>>
>>> Various improvements to compatibility test.
>>> -------------------------------------------
>>>
>>> Key: DERBY-689
>>> URL: http://issues.apache.org/jira/browse/DERBY-689
>>> Project: Derby
>>> Type: Improvement
>>> Reporter: Rick Hillegas
>>> Assignee: Rick Hillegas
>>> Attachments: bug689.diff
>>>
>>> Improve compatibility test as various reviewers requested.
>>
>>
>>
Re: [jira] Updated: (DERBY-689) Various improvements to compatibility
test.
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
Hi, Rick. I have (finally) been able to apply this patch. My goodness,
moving files/directories is a bit if a nightmare with svn diff / patch.
Did someone say there is a better patch program that can handle this?
Is there a reason you are running the compatibility tests in
derbynetmats suite? Shouldn't this be in derbynetclientmats?
derbynetmats runs with the DB2 JDBC driver, which although interesting
seems less important than the Derby JDBC driver.
Thanks,
David
Rick Hillegas (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
>
> Rick Hillegas updated DERBY-689:
> --------------------------------
>
> Attachment: bug689.diff
>
> Various improvements to compatibility test:
>
> 1) Moved all JUnit tests under a ...functionTests/tests/junitTests as Myrna and John requested.
>
> 2) Made the test harness sanity check the classpath as David requested.
>
> 3) Abstracted a CompatibilitySuite out of the original test to make it easier to add more test classes, as Francois requested.
>
> 4) Added combinations for the 10.1.2.0 client and server
>
> 5) The derbyall diff tool was enhanced to fabricate an empty canon file if one doesn't exist in the codeline. This eliminates the need to create empty canons for JUnit tests.
>
> The svn status for this patch follows:
>
> M java\testing\README.htm
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
> D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
> D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
> M java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
> M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
> A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
> A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
> M java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
> D java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
> M java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
> M java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
> M java\testing\build.xml
>
> Note that functionTests/tests/compatibility was svn moved to functionTests/tests/junitTests/compatibility and the CompatibiltiyTest itself was svn moved to functionTests/tests/junitTests/derbynet.
>
> The compatibility test suite runs cleanly on my machine and so does derbyall.
>
>
>>Various improvements to compatibility test.
>>-------------------------------------------
>>
>> Key: DERBY-689
>> URL: http://issues.apache.org/jira/browse/DERBY-689
>> Project: Derby
>> Type: Improvement
>> Reporter: Rick Hillegas
>> Assignee: Rick Hillegas
>> Attachments: bug689.diff
>>
>>Improve compatibility test as various reviewers requested.
>
>
[jira] Updated: (DERBY-689) Various improvements to compatibility test.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas updated DERBY-689:
--------------------------------
Attachment: bug689.diff
Various improvements to compatibility test:
1) Moved all JUnit tests under a ...functionTests/tests/junitTests as Myrna and John requested.
2) Made the test harness sanity check the classpath as David requested.
3) Abstracted a CompatibilitySuite out of the original test to make it easier to add more test classes, as Francois requested.
4) Added combinations for the 10.1.2.0 client and server
5) The derbyall diff tool was enhanced to fabricate an empty canon file if one doesn't exist in the codeline. This eliminates the need to create empty canons for JUnit tests.
The svn status for this patch follows:
M java\testing\README.htm
D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
D java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
D java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
M java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests
A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility
M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\README.html
M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml
A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\CompatibilitySuite.java
M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\Pinger.java
M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java
M + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\build.xml
A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet
A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest_app.properties
A + java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\CompatibilityTest.java
A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\copyfiles.ant
A java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\derbynet\build.xml
M java\testing\org\apache\derbyTesting\functionTests\harness\FileCompare.java
D java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
M java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
M java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
M java\testing\build.xml
Note that functionTests/tests/compatibility was svn moved to functionTests/tests/junitTests/compatibility and the CompatibiltiyTest itself was svn moved to functionTests/tests/junitTests/derbynet.
The compatibility test suite runs cleanly on my machine and so does derbyall.
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: http://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Type: Improvement
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: bug689.diff
>
> Improve compatibility test as various reviewers requested.
--
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] Reopened: (DERBY-689) Various improvements to compatibility
test.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reopened DERBY-689:
---------------------------------
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: https://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Rick Hillegas
> Assigned To: Rick Hillegas
> Fix For: 10.2.1.6
>
> Attachments: bug689.diff, bug689_2.diff
>
>
> Improve compatibility test as various reviewers requested.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-689) Various improvements to compatibility
test.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed DERBY-689.
-------------------------------
Resolution: Fixed
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: https://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Rick Hillegas
> Assigned To: Rick Hillegas
> Fix For: 10.2.1.6
>
> Attachments: bug689.diff, bug689_2.diff
>
>
> Improve compatibility test as various reviewers requested.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-689) Various improvements to compatibility
test.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas closed DERBY-689:
-------------------------------
> Various improvements to compatibility test.
> -------------------------------------------
>
> Key: DERBY-689
> URL: http://issues.apache.org/jira/browse/DERBY-689
> Project: Derby
> Type: Improvement
> Components: Test
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: bug689.diff, bug689_2.diff
>
> Improve compatibility test as various reviewers requested.
--
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