db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Date Tue, 09 Nov 2010 19:52:08 GMT

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

Michael Bouschen updated JDO-647:

    Attachment: JDO-647-pom-properties.zip

Hi Michelle,

the attached zip file JDO-647-pom-properties.zip changes the pom.xml files in the root directory
and in api, exectck and tck. The root pom defines properties  e.g. <junit.version>3.8.1</junit.version>
that are used in the dependency definitions of the subprojects poms. This way only the root
pom.xml defines the version number in case the same dependency occurs in multiple subprojects.
I added a <parent>...</parent> section in the poms of the subprojects to make
the properties available. 

I also changed the version number to 3.1-SNAPSHOT in all of the poms. Other than that I did
not change any version number (e.g. update the datanucleus version number). This needs to
be done afterwards.

You need to run mvn install in teh root directory. This copies the root pom in your local
mvn repository.

Regards Michael

> 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.

View raw message