Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 24517 invoked from network); 17 Dec 2007 21:23:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Dec 2007 21:23:35 -0000 Received: (qmail 82655 invoked by uid 500); 17 Dec 2007 21:23:23 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 82182 invoked by uid 500); 17 Dec 2007 21:23:22 -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 82171 invoked by uid 99); 17 Dec 2007 21:23:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2007 13:23:22 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [72.26.105.135] (HELO goku.devzuz.com) (72.26.105.135) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2007 21:23:00 +0000 Received: from [192.168.1.2] (194.108.101-84.rev.gaoland.net [84.101.108.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by goku.devzuz.com (Postfix) with ESMTP id 2B599E083FC for ; Mon, 17 Dec 2007 13:23:02 -0800 (PST) Message-ID: <4766E8B5.8050607@venisse.net> Date: Mon, 17 Dec 2007 22:23:01 +0100 From: Emmanuel Venisse User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: Confused by Continuum and Maven2 multimodule integration References: <20071217173206.GL3192@mars.cry.pto> In-Reply-To: <20071217173206.GL3192@mars.cry.pto> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org The standard maven directory structure is recommended, but you're right, it rebuild all. We must add a check in next version to know if the build generated a real artifact that require a children build Emmanuel Julien Stern a �crit : > Hi list, > > when using Maven2, it appear to be recommended to have the following > directory structure for a multi-module build: > > - pom.xml (parent pom of all modules) > --- module1 > +-- pom.xml > --- module2 > +-- pom.xml > etc > > When using such a structure with continuum, if I commit a change > in module28, then EVERY module will be rebuilt: > indeed the parent pom will be rebuilt because the change is "under" > its scm tree, and all the other modules will therefore we rebuilt > because of a "dependencies change" on the parent pom. > > When trying to avoid this, I attempted to use the following structure: > > --- parent > +-- pom.xml > --- module1 > +-- pom.xml > --- module2 > +-- pom.xml > > However, this prevents a number of M2 functionnalities, such as, for > instance, the usage of the release plugin for the whole project (as > far as I understood). > > What are the best practices when using Continuum and M2 with multimodule > builds together ? > > How does the Maven team avoids this issue when building Maven2 and > Continuum themselves with Continuum ? > > Thanks in advance. > > -- > Julien > >