Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 51511 invoked from network); 15 Nov 2008 13:42:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Nov 2008 13:42:19 -0000 Received: (qmail 49199 invoked by uid 500); 15 Nov 2008 13:42:26 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 49156 invoked by uid 500); 15 Nov 2008 13:42:26 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 49145 invoked by uid 99); 15 Nov 2008 13:42:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Nov 2008 05:42:26 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of oliver.lamy@gmail.com designates 74.125.78.147 as permitted sender) Received: from [74.125.78.147] (HELO ey-out-1920.google.com) (74.125.78.147) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Nov 2008 13:41:05 +0000 Received: by ey-out-1920.google.com with SMTP id 21so674848eyc.14 for ; Sat, 15 Nov 2008 05:41:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=5SPDS4eOdKcDSprHmZvF5LQEsorZfT9NarBSO+nXx/A=; b=ZjWV4En7bpf52q2XB0L5A/wB2XbS4uQO6i8Fx6fdM0Mjz7P3dFsIfUC1O9KN8jsEf8 ZEP8kxNfI+XGMAJgtYC4lr416reHo+HVjwGN+w5Wr3qH1qqtHbgBXpj+bTGkCl/LQxP6 fgCJoKkz4xFmZlDzHp6qPMQN9YCU6G1iecnGc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Oe9YwMbDtF30C09QiKqBlQPsBVABEyir+n6xbvqOJ1mHm+BgRK+XwROgXaVFiUH7nB NSBR0nqmlffj56Yuri3UBScXyYSlchBDNUciuWM/XMSKgRKJYFIrATwC+PN/lPEOJYaR vqnuRQ/0st2UZbOZWEkIlE2L6y+boD1uAFswE= Received: by 10.103.249.19 with SMTP id b19mr651850mus.86.1226756498878; Sat, 15 Nov 2008 05:41:38 -0800 (PST) Received: by 10.102.215.4 with HTTP; Sat, 15 Nov 2008 05:41:38 -0800 (PST) Message-ID: <9948cb690811150541x104f6992kc9312c75414e93f0@mail.gmail.com> Date: Sat, 15 Nov 2008 14:41:38 +0100 From: "Olivier Lamy" Sender: oliver.lamy@gmail.com To: users@continuum.apache.org Subject: Re: Continuum 1.1 / 1.2 and multiple modules In-Reply-To: <5F07FEF8-7E84-4056-980B-5292FDF95F45@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20511352.post@talk.nabble.com> <5F07FEF8-7E84-4056-980B-5292FDF95F45@gmail.com> X-Google-Sender-Auth: 43f7e5639deabde2 X-Virus-Checked: Checked by ClamAV on apache.org 2008/11/15 Fabien Tillay : > Si I'm gonna reformulate my question : > Is it possible with Continuum 1.1 or 1.2 to build a parent pom recursivel= y : > > - With this structure > > Root > -parent > ----->pom.xml > -moduleA > ----->pom.xml > -moduleB > ----->pom.xml > > > > - With this structure > > Root > -pom.xml > -moduleA > ----->pom.xml > -moduleB > ----->pom.xml > Yes use this structure (when adding the project use the checkbox with "For multi modules project, load only root as recursive build" or "Pour les projets multi modules, charger uniquement la racine comme une construction r=E9cursive" in the Moli=E8re language :-) ). I use at work wihout any issue. -- Olivier > > Thanks > > Le 15 nov. 08 =E0 02:51, Wendy Smoak a =E9crit : > >> On Fri, Nov 14, 2008 at 6:37 PM, silver95 wrote: >> >>> Does Continuum 1.1 and 1.2 can manage this structure ? >>> It seems that it does not understand relative path (ie ../moduleA and >>> ../moduleB) >> >> Based on my tests, Continuum 1.2 _can_ handle this "flat" structure >> when adding the project and building all projects in the group. >> >> Limitations I'm aware of: >> - you can't use the release process at the group level >> - a recursive build from the parent won't work >> >> See this issue for more info and a sample project: >> http://jira.codehaus.org/browse/CONTINUUM-1850 >> >> -- >> Wendy > >