Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
If a willing volunteer ever tries to run the JDO TCK on a datastore other than Derby they will logically want to use the exectck plugin ... even for the enhancer + runtck parts. Using "install" will invoke it but will attempt to run installSchema also. This is currently hardcoded to Derby and so will spit out lots of errors due to absence of Derby etc. All datastores have their own schema generation process so would be hard to provide a unified approach.
Adding a simple check to the required datastore being "derby" and only running then would be a simple addition.