Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <410773.1212773385021.JavaMail.jira@brutus>
Date: Fri, 6 Jun 2008 10:29:45 -0700 (PDT)
From: =?utf-8?Q?J=C3=B6rg_von_Frantzius_=28JIRA=29?= <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Commented: (JDO-596) Upgrade to maven 2
In-Reply-To: <373050006.1212195765069.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JDO-596?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1260311=
0#action_12603110 ]=20

J=C3=B6rg von Frantzius commented on JDO-596:
----------------------------------------

Just to have mentioned it, maven2 profiles plus cargo and junitee plugins m=
ake it fairly easy to run tests on combinations of various appservers (as s=
upported by cargo) and transaction types (JTA or JCA).

If eventually JDO TCK moves to maven2, you may want to have a look at https=
://datanucleus.svn.sourceforge.net/svnroot/datanucleus/test/test.appservers=
/trunk

> Upgrade to maven 2
> ------------------
>
>                 Key: JDO-596
>                 URL: https://issues.apache.org/jira/browse/JDO-596
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>            Reporter: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 2
>
>
> It would be a good idea to use maven 2. This involves rewriting the custo=
m goals in maven.xml as Java plugins, among other things.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.