Hi Craig,
two minor comments:
Please mention that we are using maven 1 (recommended version is maven
1.0.2). We do not run with maven 2.
Section "Running the Tests" describes to use 'maven multiproject:build'
to build the requires jars. This works because the distribution does not
contain a
The installSchema goal is only handling derby database. Should't exist a generic
implementation that connects to any database using a jdbc driver, reads and
fires sql scripts to database B, C or D?
Quoting Michael Bouschen <[EMAIL PROTECTED]>:
> Hi Craig,
>
> > Javadogs,
> >
> > I'm inclined to a
Hi Craig,
Javadogs,
I'm inclined to agree with Andy that the schema and orm files for each
of the databases we know of should be standard and specified as part of
the TCK.
I agree.
There is nothing in the TCK tests that should be different in the orm
files from one database to another.
Javadogs,I'm inclined to agree with Andy that the schema and orm files for each of the databases we know of should be standard and specified as part of the TCK.There is nothing in the TCK tests that should be different in the orm files from one database to another. There are differences in the sche
Hi Craig,
> Attached please find the first draft of the TCK run rules for JDO
> 2.0. Please comment.
Why is the "sql" modifiable "to suit the JDO implementation" ?
Why is the "orm" modifiable "to suit the JDO implementation" ?
Surely the ORM defines the underlying schema, and so the ORM files pr
Javadogs,Attached please find the first draft of the TCK run rules for JDO 2.0. Please comment.Craig
Running the JDO 2.0 Technology Compatibility Kit
Overview
In order to demonstrate compliance with the Java Data Objects
specification, an implementation must successfully run all of the TCK
tests
