db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JDO-647) Run TCK using Maven2 for consistency
Date Fri, 27 Jan 2012 10:14:40 GMT

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

Andy Jefferson updated JDO-647:

    Attachment: JDO-647-default-cfgList.patch

This patch removes hardcoded cfgList and reads it from src/conf/configurations.list, meaning
that when people add a new test to the tck they just add it in configurations.list
> Run TCK using Maven2 for consistency
> ------------------------------------
>                 Key: JDO-647
>                 URL: https://issues.apache.org/jira/browse/JDO-647
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck
>    Affects Versions: JDO 3 (3.0)
>            Reporter: Andy Jefferson
>            Assignee: Michelle Caisse
>             Fix For: JDO 3 maintenance release 1 (3.1)
>         Attachments: JDO-647-default-cfgList.patch, JDO-647-pom-properties.zip, JDO-647-rootPomChanges.patch,
RunRules.patch, api_pom.diff, exectck.zip, exectck.zip, pom.xml, pom.xml
> Since api2 now builds using Maven2 it makes a heck of a lot of sense to build/run the
TCK using that too. It also means that the DataNucleus M1 repo (which only exists for use
of this TCK) can be deleted. Please consider upgrading to Maven2

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