I'd rather not spend time - making a patch and all that...- on it right now. Maybe you can fix it and commit it too?
(That is, you *are* a committer? Didn't see your name on: http://db.apache.org/whoweare.html)
:-)
Myrna
On 11/1/05, David W. Van Couvering <[EMAIL PROTECTED]> wrote:
OK, that's good to know. It looks like I and others have been misled
that we had to pull these jars down to run tests. Note Bryan's recent
efforts to get these jars -- I think he was just following the
instructions in BUILDING.txt.
I can log a JIRA to fix the wording in testing/README.htm to make it
clear that the DB2 driver is optional (and thus the derbynet tests are
optional).
David
Daniel John Debrunner wrote:
> David W. Van Couvering wrote:
>
>
>>I hope I'm not stepping on a landmine here, but does anyone else who
>>thinks it would be a good thing to remove the need for the DB2 JDBC
>>driver for our builds and tests? It's fine if it's an optional part,
>>like support for JDK 1.6, but it doesn't seem right that it's required
>>now that we have our own JDBC driver...
>
>
> Dumb question, in what way is it required?
>
> I thought it was alredy optional.
>
> As far as I know it is not needed for building.
>
> As far as I know the derbynet tests will be skipped if it is not in the
> class path.
>
> I thought that this had been the case since Derby was open sourced.
>
> Dan.
>
