Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 76658 invoked from network); 3 May 2009 21:24:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 May 2009 21:24:51 -0000 Received: (qmail 97212 invoked by uid 500); 3 May 2009 21:24:51 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 97202 invoked by uid 99); 3 May 2009 21:24:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 May 2009 21:24:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 May 2009 21:24:50 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5A757234C003 for ; Sun, 3 May 2009 14:24:30 -0700 (PDT) Message-ID: <1231252352.1241385870354.JavaMail.jira@brutus> Date: Sun, 3 May 2009 14:24:30 -0700 (PDT) From: "Craig Russell (JIRA)" 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: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JDO-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705447#action_12705447 ] Craig Russell commented on JDO-596: ----------------------------------- In my workspace I have a pom.xml parallel to trunk: 4.0.0 javax.jdo root 2.3-SNAPSHOT pom I think this is a better solution since in future we can avoid changing poms in each subproject and simply update the version number in trunk (or in branches/2.3) to have the right version number. > Upgrade to maven 2 > ------------------ > > Key: JDO-596 > URL: https://issues.apache.org/jira/browse/JDO-596 > Project: JDO > Issue Type: Improvement > Components: api2 > Reporter: Michelle Caisse > Assignee: Craig Russell > Priority: Minor > Fix For: JDO 2 maintenance release 3 > > Attachments: jdo-596.patch > > > It would be a good idea to use maven 2. This involves rewriting the custom goals in maven.xml as Java plugins, among other things. > This is for the JDO API not for the JDO TCK. We need a separate issue for the corresponding TCK change. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.