db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-647) Run TCK using Maven2 for consistency
Date Mon, 17 Oct 2011 14:01:11 GMT

    [ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128888#comment-13128888
] 

Andy Jefferson commented on JDO-647:
------------------------------------

+1 to Michaels last comment about having a log file per configuration; debugging something
is made much harder by having to manually run each individual test separately to get the log
just for that test
                
> 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
>            Reporter: Andy Jefferson
>            Assignee: Michelle Caisse
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: 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

        

Mime
View raw message