Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 71138 invoked from network); 22 Apr 2006 19:29:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Apr 2006 19:29:37 -0000 Received: (qmail 92795 invoked by uid 500); 22 Apr 2006 19:29:35 -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 92776 invoked by uid 99); 22 Apr 2006 19:29:35 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Apr 2006 12:29:35 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Apr 2006 12:29:34 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CFA1F7142E1 for ; Sat, 22 Apr 2006 19:28:15 +0000 (GMT) Message-ID: <4727929.1145734095848.JavaMail.jira@brutus> Date: Sat, 22 Apr 2006 19:28:15 +0000 (GMT+00:00) From: "Michael Bouschen (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Reopened: (JDO-51) Improve documentation on build dependencies MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JDO-51?page=all ] Michael Bouschen reopened JDO-51: --------------------------------- > Improve documentation on build dependencies > ------------------------------------------- > > Key: JDO-51 > URL: http://issues.apache.org/jira/browse/JDO-51 > Project: JDO > Type: Improvement > Components: tck20 > Reporter: Michelle Caisse > Assignee: Michael Bouschen > > Michael B's summary: > yes, we need to describe the dependencies in the README.txt. I propose the following build order: > JDO1: api11, btree, ri11, tck11 > JDO2: api20, tck20 > Another alternative is using the multiproject support of maven. You can call 'maven -Dgoal=build multiproject:goal' in the directory trunk. Then maven looks at all the subprojects and calculates a dependency graph using the specified dependencies in the project.xml file. It then executes the goal build in all the subprojects in the order of the calculated dependencies. The only downside is that it does it for all the subprojects, so for the jdo1 and jdo2 subprojects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira