Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <2963033.320091290744614166.JavaMail.jira@thor>
Date: Thu, 25 Nov 2010 23:10:14 -0500 (EST)
From: "Michelle Caisse (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michelle Caisse commented on JDO-647:
-------------------------------------

Checked in the exectck project and the tck's pom.xml. When running "mvn integration-test", datanucleus does not appear to receive the schema information, thus tables are not found.

> 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: api_pom.diff, exectck.zip, exectck.zip, JDO-647-pom-properties.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.
-
You can reply to this email to add a comment to the issue online.