db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JDO-715) exectck will always try to install Derby schema even if derby not being run
Date Sat, 02 Jun 2012 06:22:23 GMT

     [ https://issues.apache.org/jira/browse/JDO-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andy Jefferson resolved JDO-715.

       Resolution: Fixed
    Fix Version/s: JDO 3 maintenance release 1 (3.1)

SVN turnk now has this
> 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
>             Fix For: JDO 3 maintenance release 1 (3.1)
>         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


View raw message