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 stephen.alan.connolly@gmail.com
 designates 209.85.214.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=ZWvqgUE2pf/eDtvyirGYo0rE60DEGCCRvVBQfBNL1KnG8W14Wj1nppZLMG9chwGqRh
         gOM8YB/c5X9HqHjw8n018gzgBkUjWnXWHGo6gbZhkLcxhslvh6QUWaDl2H6zh0HU50kV
         iyQ1IM4GFwYkHuvw+bf1+5dCjRnH+CsRZA6WY=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=8Ok3GfHcMjoLpdPGSYNMMtyQCV5A1CsM4Jzr0@mail.gmail.com>
References: <AANLkTiny+u5x=eD=7NZFXMc_c9o9ckHsGKq7dzuK_fwa@mail.gmail.com>
	<AANLkTikZC2E3+m58Q35ziCiCQJp1hnSFus97R4RemV4j@mail.gmail.com>
	<AANLkTinSCDQEhce=yo0mVxk56webiR2o5ZVrBWqeuJKv@mail.gmail.com>
	<AANLkTi=8Ok3GfHcMjoLpdPGSYNMMtyQCV5A1CsM4Jzr0@mail.gmail.com>
Date: Tue, 5 Oct 2010 22:23:48 +0100
Message-ID: <AANLkTimRTa6fgvR-_SFEUg8fy5APG_1XgvoT2L4nNZrf@mail.gmail.com>
Subject: Re: Continuous Build always building against the latest SNAPSHOT
 version
From: Stephen Connolly <stephen.alan.connolly@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

what i've done before is use the versions:use-latest-versions goal in
an initial maven invocation and then follow up with clean verify and
finally a versions:rollback so that the next svn update does not get
borked.

I'd typically have a couple of jobs on the CI server, one building
exactly what is in scm, one building with the latest releases and one
building with the very latest.

If using hudson, you will have to use a freestyle project (which is
IMHO the only way to build maven projects in hudson) and have three
maven build steps... versions-maven-plugin modifies the pom and so you
need to start a new maven process to see the effects

-Stephen

On 5 October 2010 21:41, Wendy Smoak <wsmoak@gmail.com> wrote:
> On Tue, Oct 5, 2010 at 4:27 PM, Mike Lenner <mike.lenner@gmail.com> wrote:
>
>> Maybe part of the release process of shared-util should be to update
>> some parent pom's dependencyManagement section to the 1.1-SNAPSHOT?
>
> Or send out a release announcement to their users list, which
> project-2's developers should be on? :)
>
> I believe the versions plugin has a goal that checks for newer
> releases of your dependencies, that might be useful.
> http://mojo.codehaus.org/versions-maven-plugin/
>
> And some of the repository managers (Archiva at least) have feeds you
> can watch for updates on artifacts.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org