From continuum-users-return-2862-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Mon Nov 06 13:44:39 2006 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 92661 invoked from network); 6 Nov 2006 13:44:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Nov 2006 13:44:38 -0000 Received: (qmail 50065 invoked by uid 500); 6 Nov 2006 13:44:47 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 50039 invoked by uid 500); 6 Nov 2006 13:44:47 -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 50018 invoked by uid 99); 6 Nov 2006 13:44:47 -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 05:44:47 -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.181.217.72] (HELO posten.jadestone.se) (62.181.217.72) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Nov 2006 05:44:32 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by posten.jadestone.se (Postfix) with ESMTP id 7346F4A115 for ; Mon, 6 Nov 2006 14:44:11 +0100 (CET) Received: from posten.jadestone.se ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29320-73 for ; Mon, 6 Nov 2006 14:44:01 +0100 (CET) Received: from STENDUM (66.217.181.62.in-addr.dgcsystems.net [62.181.217.66]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by posten.jadestone.se (Postfix) with ESMTP id F1B934A10F for ; Mon, 6 Nov 2006 14:44:00 +0100 (CET) From: =?iso-8859-1?Q?Petter_M=E5hl=E9n?= To: Subject: Project build order Date: Mon, 6 Nov 2006 14:43:54 +0100 Message-ID: <031901c701a9$9a2b0580$0b02a8c0@jadestone.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AccBqZnVq2PZvxnWQsaBmgDhE2rX7w== X-Virus-Scanned: by amavisd-new at jadestone.se X-Virus-Checked: Checked by ClamAV on apache.org 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 = with common message definitions for node-node communication being updated. 2. 'mvn clean install' for project 'server': we have written a simple = Maven 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 = code 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 = executed in. It may be relevant that the 'server->common' dependency is = configured like so: ... =20 se.jadestone.whine maven-whine-generator 3.0 ... =20 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