Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 63127 invoked from network); 6 Nov 2006 16:50:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Nov 2006 16:50:48 -0000 Received: (qmail 83943 invoked by uid 500); 6 Nov 2006 16:50:58 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 83927 invoked by uid 500); 6 Nov 2006 16:50:58 -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 83916 invoked by uid 99); 6 Nov 2006 16:50:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Nov 2006 08:50:58 -0800 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 [62.193.206.9] (HELO webmail9.amenworld.com) (62.193.206.9) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 06 Nov 2006 08:50:43 -0800 Received: (qmail 4783 invoked from network); 6 Nov 2006 16:50:28 -0000 Received: from unknown (HELO ?127.0.0.1?) (81.185.104.149) by 0 with SMTP; 6 Nov 2006 16:50:28 -0000 Message-ID: <454F67C9.9030103@venisse.net> Date: Mon, 06 Nov 2006 17:50:17 +0100 From: Emmanuel Venisse User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: Diverse Repositories References: <265E9EE670ED404DA5DBE42428204A4429FA5E@uscnt0416.us.deloitte.com> In-Reply-To: <265E9EE670ED404DA5DBE42428204A4429FA5E@uscnt0416.us.deloitte.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org You need to add them separately. If you have children projects in three sources repositories, you'll need to add three projects in Continuum (one by child) Emmanuel Morgovsky, Alexander (US - Glen Mills) a �crit : > Right, but if I have separate projects which cannot be tied to one parent project because the same svn information will be assumed for the child projects, how should I aggregate the child projects if I am not allowed to add them as modules? Thanks. > > -----Original Message----- > From: Emmanuel Venisse [mailto:emmanuel@venisse.net] > Sent: Monday, November 06, 2006 11:38 AM > To: continuum-users@maven.apache.org > Subject: Re: Diverse Repositories > > Continuum find the correct order for the build with the dependencies list. > > Emmanuel > > Morgovsky, Alexander (US - Glen Mills) a �crit : >> If I have three diverse children, and each one of these has submodules themselves, should I consider these to be three children independent of each other and separately add them to the Continuum build? If so, if the order of building them is A, C, and B, for example, how should I configure the order in which Maven 2 builds these, since I cannpt declare them in the main parent anymore? Thanks. >> -----Original Message----- >> From: Emmanuel Venisse [mailto:emmanuel@venisse.net] >> Sent: Monday, November 06, 2006 11:22 AM >> To: continuum-users@maven.apache.org >> Subject: Re: Diverse Repositories >> >> If children are in different souce repositories, I considerate them as different project and mustn't >> be declare as module in your parent pom. >> >> The file protocol is already supported (since the first version), but it is desactivated by default. >> http://maven.apache.org/continuum/faqs.html#can-i-use-file-protocol-in-add-project-view >> >> Emmanuel >> >> Morgovsky, Alexander (US - Glen Mills) a �crit : >>> What work-around do you recommend for me to use if I have children which >>> are housed in different source code repositories from the parent, since >>> the source code repository which is read from the parent is assumed for >>> the children? Will the file:// protocol work here? >>> >>> >>> This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. >>> >>> >>> Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] >>> >> >> >> > > > >