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?
