From continuum-users-return-2878-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Mon Nov 06 17:41:11 2006 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 79713 invoked from network); 6 Nov 2006 17:41:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Nov 2006 17:41:10 -0000 Received: (qmail 97310 invoked by uid 500); 6 Nov 2006 17:41:21 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 96920 invoked by uid 500); 6 Nov 2006 17:41:20 -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 96909 invoked by uid 99); 6 Nov 2006 17:41:20 -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 09:41:20 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of waynefay@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Nov 2006 09:41:06 -0800 Received: by ug-out-1314.google.com with SMTP id j40so825018ugd for ; Mon, 06 Nov 2006 09:40:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O/BxV62/HzhAVzRkQmnjNkIFsbwDcn5FFfZHtDU6ilmmCgjKnLcMbow/5Yrs1WjlQMX4Jw4tZwQDhauMXWZglakatG7K/I7GQdybML8ftAzVTKTTY9Ucr48+0jxHMQrpg77agCgVqXuPqZUv5WXK1PLzSvSrTcV9pfGLcgOVrys= Received: by 10.78.193.19 with SMTP id q19mr7025289huf.1162834844330; Mon, 06 Nov 2006 09:40:44 -0800 (PST) Received: by 10.78.117.2 with HTTP; Mon, 6 Nov 2006 09:40:44 -0800 (PST) Message-ID: <52bab8690611060940k7f47952dx8d5f12206e6fafa6@mail.gmail.com> Date: Mon, 6 Nov 2006 11:40:44 -0600 From: "Wayne Fay" To: continuum-users@maven.apache.org Subject: Re: Project build order In-Reply-To: <031901c701a9$9a2b0580$0b02a8c0@jadestone.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <031901c701a9$9a2b0580$0b02a8c0@jadestone.local> X-Virus-Checked: Checked by ClamAV on apache.org Sounds to me like Client depends on Server depends on Common. Thus: common/pom.xml ...none... server/pom.xml ...common... client/pom.xml ...server, common... or ...server... and common will be pulled in via transitive dependencies Is there a reason you can't set things up like this, or why this won't work for you? Wayne On 11/6/06, Petter M=E5hl=E9n wrote: > Hi, > > I have a question concerning what I can do to force projects to be built = in > a specific order. There have been some previous similar queries, but they > don't quite seem to apply to our situation. What we want is this: > > 1. 'mvn clean install' for project 'common': this leads to a jar file wit= h > common message definitions for node-node communication being updated. > 2. 'mvn clean install' for project 'server': we have written a simple Mav= en > plugin that reads the message definitions, and generates source code that > parses/packages the messages. > 3. 'ant clean test' for project 'client': this again generates source cod= e > for parsing/packaging messages, but this time for the client. > > Is it possible for us to specify this order somehow? As it is, the builds > will more or less randomly fail depending on which order they are execute= d > in. It may be relevant that the 'server->common' dependency is configured > like so: > > > ... > > > > se.jadestone.whine > maven-whine-generator > 3.0 > ... > > > se.jadestone.esports > hc-common > 0.0.1 > > > > ... > > The 'common' jar must be available on the classpath of the plugin that > generates source code, and like this, it is only available at that point, > which is great since we don't want to include it in the shipped product. > > Thanks for any help, > > Petter > > Cell: +46 704 40 30 25 > Direct: +46 8 442 75 95 > Fax: +46 8 24 05 08 > www.jadestone.se > Bj=F6rns Tr=E4dg=E5rdsgr=E4nd 1, 116 21 Stockholm, Sweden > >