From continuum-users-return-3820-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Mon May 21 16:39:10 2007 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 87276 invoked from network); 21 May 2007 16:39:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 16:39:09 -0000 Received: (qmail 49418 invoked by uid 500); 21 May 2007 16:39:13 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 49401 invoked by uid 500); 21 May 2007 16:39:12 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 49390 invoked by uid 99); 21 May 2007 16:39:12 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 09:39:12 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [217.12.11.62] (HELO smtp008.mail.ukl.yahoo.com) (217.12.11.62) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 21 May 2007 09:39:03 -0700 Received: (qmail 55001 invoked from network); 21 May 2007 16:38:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Received:X-YMail-OSG:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-MimeOLE:In-Reply-To:Thread-Index; b=uKtBHJ2I0/W9fLEPVHKSvyEP5Q6m31ZaccGvl2ZpwR9R8y+MMw3HvbpiBVVwDCFABkYK082B/o0dXrVqWrJut4S7UJG/iyRZYVesKwuV8kBXRHLQLMw3uR6fo3HQ12WUpzP0Y1IbNjrwi5i868JSj6KkmMd1WPzaeCqEaIhbZZI= ; Received: from unknown (HELO MIQSBARRIBA) (sbarriba@81.149.172.165 with login) by smtp008.mail.ukl.yahoo.com with SMTP; 21 May 2007 16:38:41 -0000 X-YMail-OSG: OqBVCmcVM1ltxW7N1RI5CXRg00VrMJqDF0uabrH8.byRPq.YLaySa7T_v9YWE75umw5tm_mgCOG.vCmr72mf8NqqFxuSBS83JY8ZSluMqkxxTRSi From: "Shaun Barriball" To: Subject: RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Date: Mon, 21 May 2007 17:38:46 +0100 Message-ID: <004e01c79bc6$80bd2da0$7201a8c0@mobileiq.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: <7CA45EC6F903DA4EB4ADB6D08D24B0F62B53BCDB@fnbfdtmx01.fnb.co.za> Thread-Index: AcebjDMObpjQURZNQX21v7mwNXNpbgAB821gAAyX6HA= X-Virus-Checked: Checked by ClamAV on apache.org We're just trying the upgrade to 1.1 now from 1.0.3. Is there an upgrade path for this which preserves the database or do we have to re-install all projects from scratch? 1.1 isn't mentioned on http://maven.apache.org/continuum/upgrade.html. Regards, Shaun. -----Original Message----- From: Jeffery, Mark [mailto:MJeffery@fnb.co.za] Sent: 21 May 2007 11:38 To: continuum-users@maven.apache.org Subject: RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Yeah.....I am battling with the same thing http://jira.codehaus.org/browse/CONTINUUM-998 Should be fixed in 1.1-alpha-# Jeff -----Original Message----- From: Shaun Barriball [mailto:sbarriba@yahoo.co.uk] Sent: 21 May 2007 11:41 To: continuum-users@maven.apache.org Subject: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Hi all, We've been using Continuum (1.0.3) successfully as part of our automated build and deploy for 6 months or so. We have one big issue which I'd appreciate input on. We have a large software system with 15 or so separate Maven 2 projects (assume for simplicity Project A, Project B and Project C) which each have sub-modules. Assume the dependency tree is: A -> depends on C -> depends on B (for example). These dependencies are expressed using Maven 2 dependency hierarchy. The "Build All" function on Continuum appears to ignore any Maven 2 dependency hierarchy and simply builds them in alphabetical order of the Project Name. This therefore builds the above example out of order - often resulting in build failures. * Should continuum 'understand' the dependency tree? I've read some material which implies this should potentially be the case (http://jira.codehaus.org/browse/CONTINUUM-39). * If not, is there a way to organise the build order for "Build All" above and beyond altering the project names with "1.", "2." etc (which is obviously undesirable)? All help appreciated. Regards, Shaun. To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the Disclaimer.