[
https://issues.apache.org/jira/browse/JDO-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-715:
-------------------------------
Attachment: JDO-715.patch
Patch that only processes schema if "derby" is the selected datastore
> exectck will always try to install Derby schema even if derby not being run
> ---------------------------------------------------------------------------
>
> Key: JDO-715
> URL: https://issues.apache.org/jira/browse/JDO-715
> Project: JDO
> Issue Type: Task
> Components: tck
> Reporter: Andy Jefferson
> Attachments: JDO-715.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
