You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Craig L Russell (JIRA)" <ji...@apache.org> on 2010/08/13 18:20:19 UTC

[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency

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

Craig L Russell commented on JDO-647:
-------------------------------------

I'd like to see a diff of the pom in the api project versus your generated pom here.

The pom for the tck is a good start. Ok to check in so we can at least start to compile using mvn while working on the running of the tck as a mvn integration phase item.

> 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: 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.
-
You can reply to this email to add a comment to the issue online.