Return-Path: 
 <users-return-99528-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: (qmail 40051 invoked from network); 16 Apr 2009 15:27:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 16 Apr 2009 15:27:16 -0000
Received: (qmail 52758 invoked by uid 500); 16 Apr 2009 15:27:13 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 52652 invoked by uid 500); 16 Apr 2009 15:27:13 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 52642 invoked by uid 99); 16 Apr 2009 15:27:13 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Apr 2009 15:27:13 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of skavish@gmail.com designates
 74.125.46.155 as permitted sender)
Received: from [74.125.46.155] (HELO yw-out-1718.google.com) (74.125.46.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Apr 2009 15:27:06 +0000
Received: by yw-out-1718.google.com with SMTP id 9so361915ywk.6
        for <users@maven.apache.org>; Thu, 16 Apr 2009 08:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :from:date:message-id:subject:to:content-type;
        bh=21j1gGXuwkfjtLXKvlYP4EauiodEBaROHcFNEgELvG0=;
        b=toTD8dmFt3T9tVPAleVlHNfM9eN2Q0+dRaDrR53AfNbYCOeilxeEPgHiqYDLTh1z5i
         qIFUdk8XCZXLios1MS+q0woZojuHPZMpRNvpOE3OzXg7tL623xUYL6yKXQr17AZ5ZYl6
         QXzd7G9/yHR2xTHpJWIe16kEg2BUwJagNV2Us=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=xiUnuYtLARk5qg9hBZfFOgAV7X0D2GgluFuNdbs3m7H31MG3CR8CeVZAYZtoAYMoqa
         6wxbrY7nEesUzow6TkZwgj6NEc7JHJX1/7GcIBbM+DmRS1e0r3t1rSkIiC9l8hltc1Cw
         gTTQcgtsNLHF9DaC5D5Pf2Zb0j6c2pCltlynM=
MIME-Version: 1.0
Received: by 10.150.177.20 with SMTP id z20mr2154118ybe.192.1239895605377;
	Thu, 16 Apr 2009 08:26:45 -0700 (PDT)
In-Reply-To: <d049fb4f0904160719j11971c26hc7ea7f0f4274a1de@mail.gmail.com>
References: <d049fb4f0904160719j11971c26hc7ea7f0f4274a1de@mail.gmail.com>
From: Dmitry Skavish <skavish@gmail.com>
Date: Thu, 16 Apr 2009 11:26:30 -0400
Message-ID: <2b4ee9820904160826o3330ade1qfced33192f7fade0@mail.gmail.com>
Subject: Re: Multi-module build is not building with current module source
	code
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=000e0cd6a95c1df9770467adb15f
X-Virus-Checked: Checked by ClamAV on apache.org

--000e0cd6a95c1df9770467adb15f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I am having the same problem and would like to know that as well. Thanks!

On Thu, Apr 16, 2009 at 10:19 AM, David Hoffer <dhoffer6@gmail.com> wrote:

> I have a multi-module build where some modules are dependent on other
> modules.  What is happening is that the dependent module is getting its
> dependency from the local/corporate maven repo instead of the source code
> that was just built.  How do I specify that modules always build using
> current source not prior built snapshot jars?
>
> Here is an example of the problem (it is really simple)
>
> Parent pom:
> <version>0.1-SNAPSHOT</version>
> <modules>
>        <module>public</module>
>        <module>internal</module>
>        <module>security-public</module>
> </modules>
>
> public pom:
> <version>0.1-SNAPSHOT</version>
>
> internal pom:
> <dependencies>
>        <dependency>
>            <groupId>${project.groupId}</groupId>
>            <artifactId>public</artifactId>
>            <version>0.1-SNAPSHOT</version>
>        </dependency>
> </dependencies>
>
> security-public:
> <dependency>
>            <groupId>${project.groupId}</groupId>
>            <artifactId>public</artifactId>
>            <version>0.1-SNAPSHOT</version>
> </dependency>
>
> So what is happening is that instead of internal  & security-public
> building
> using the just built public (note it is first so it was built first) they
> go
> out and download the last deployed snapshot and build using that instead.
>
> Nothing in the pom dependency syntax really says which to use but I assumed
> that because maven 'knows' these are all in the reactor it would use module
> source.  However this doesn't seem to work, what do I need to do to fix
> this?
>
> BTW, the goals being run are 'clean deploy site-deploy'
>
> -Dave
>



-- 
Dmitry Skavish

--000e0cd6a95c1df9770467adb15f--