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.
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
