Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of anders.g.hammar@gmail.com
 designates 209.85.216.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=AW/RBIzBtlDuN7zKxXQrEzvZbih+6yBVlf+ozQgpEJ+ZUGosHTSDx2smfVmDegoIel
         HKec+SLnS3fqWLyAKCanXLRKL1Wy1pbgNfXs40HNhghFfdUX1U5SPXvzJNYPo0UqSAVs
         V2BX3oQv+OPK/znhPUjJ/EtKMnLPyRXPiDSGk=
MIME-Version: 1.0
Sender: anders.g.hammar@gmail.com
In-Reply-To: <AANLkTiny+u5x=eD=7NZFXMc_c9o9ckHsGKq7dzuK_fwa@mail.gmail.com>
References: <AANLkTiny+u5x=eD=7NZFXMc_c9o9ckHsGKq7dzuK_fwa@mail.gmail.com>
Date: Tue, 5 Oct 2010 22:10:17 +0200
Message-ID: <AANLkTikZC2E3+m58Q35ziCiCQJp1hnSFus97R4RemV4j@mail.gmail.com>
Subject: Re: Continuous Build always building against the latest SNAPSHOT
 version
From: Anders Hammar <anders@hammar.net>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=001517503cc8e6ff400491e43fac

--001517503cc8e6ff400491e43fac
Content-Type: text/plain; charset=ISO-8859-1

I don't see that you're doing anything wrong. You just need to bump the dep
version in project-2. Or, I guess, you could use version ranges but I'm kind
of allergic to them so I'd suggest stay off that path.

/Anders
On Tue, Oct 5, 2010 at 22:05, Mike Lenner <mike.lenner@gmail.com> wrote:

> Any help would be greatly appreciated - I'm trying to figure out how
> to do this the maven way.
>
> I have a shared dependency called shared-util.  My team frequently
> makes changes to our deployable projects along with changes to the
> shared-util.  So, in my continuous build, I'd like each of our
> projects always building against the latest shared-util.
>
> Seems like a perfect situation for a SNAPSHOT dependency.  So,
> project-1 and project-2 each depend on 1.0-SNAPSHOT of shared-util.
> Continuous Build deploys the current 1.0-SNAPSHOT to our repo after
> each code commit, and project-1 and project-2 build fine.
>
> But then we release project-1.  We don't want to do so with SNAPSHOT
> dependencies, so we release shared-util as well.  The maven release
> plugin updates shared-util to 1.1-SNAPSHOT after the release (as well
> as project-1's dependency).
>
> But now project-2, still dependent on 1.0-SNAPSHOT, is no longer
> building against the latest shared-util.  Future commits to
> shared-util will not be built against in our Continuous Build for
> project-2 because project-2 is dependent on a "dead" snapshot.
>
> What am I missing / doing wrong here?  Seems like snapshots were made
> for this use case.
>
> Thanks,
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--001517503cc8e6ff400491e43fac--