From jdo-dev-return-8183-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Fri Jun 19 16:37:52 2009 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 20572 invoked from network); 19 Jun 2009 16:37:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jun 2009 16:37:51 -0000 Received: (qmail 22842 invoked by uid 500); 19 Jun 2009 16:24:32 -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 22831 invoked by uid 99); 19 Jun 2009 16:24:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 16:24:31 +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; Fri, 19 Jun 2009 16:24:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8ABD229A0015 for ; Fri, 19 Jun 2009 09:24:07 -0700 (PDT) Message-ID: <1658499340.1245428647567.JavaMail.jira@brutus> Date: Fri, 19 Jun 2009 09:24:07 -0700 (PDT) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Updated: (JDO-596) Provide maven 2 POM 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:all-tabpanel ] Craig Russell updated JDO-596: ------------------------------ Description: Provide a proper Maven 2 pom for use with JDO. Build and test JDO with the new POM. Update the build instructions on how to publish the new POM for use with Maven 2. (was: 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. ) Summary: Provide maven 2 POM (was: Upgrade to maven 2) This issue has represented several things but what we agreed to do is to make JDO compatible with Maven 2 but deferred the decision on how to build JDO and run the TCK to later. > Provide maven 2 POM > ------------------- > > 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 > > > Provide a proper Maven 2 pom for use with JDO. Build and test JDO with the new POM. Update the build instructions on how to publish the new POM for use with Maven 2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.