On 11/1/05, Daniel John Debrunner <[EMAIL PROTECTED]> 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.
Yes. However, it's not explicit in the testing/README.htm, and the section on setting up the CLASSPATH includes db2jcc.jar. An oversight. We should add a ('optional') behind those jars.
Myrna
