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 (athena.apache.org: domain of sirlyric@gmail.com designates
 209.85.198.247 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
         :content-transfer-encoding;
        b=tv/vs673hphjxpUg8x8E1FbmPoj8+PJ2Pn5Fvy1s4P/kX7a+twUMcdUyVjJAudmo9x
         yF4ifSuZAX950bCbN1IcCL3hqPSHxqJTlrDeag4DlgvgN66kkTeeoDBr2QotYroAkB+A
         9YtbPsgbtLNERLaaIvBQsmE+ZScZJv/j2DuW0=
MIME-Version: 1.0
Sender: sirlyric@gmail.com
In-Reply-To: <c7c567b10901190401r39927734u6002ff3762089fb5@mail.gmail.com>
References: <c7c567b10901190316i1bc7cf09i23a00eb41e311b32@mail.gmail.com>
	 <235405.32597.qm@web27807.mail.ukl.yahoo.com>
	 <c7c567b10901190401r39927734u6002ff3762089fb5@mail.gmail.com>
Date: Mon, 19 Jan 2009 11:17:12 -0500
Message-ID: <2c6c17340901190817t337a5018re349e2672bcd79bd@mail.gmail.com>
Subject: Re: Perform release without updating pom to new SNAPSHOT version
From: John Stoneham <lyric@lyrically.net>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Mon, Jan 19, 2009 at 7:01 AM, Wim Deblauwe <wim.deblauwe@gmail.com> wrote:
> No, we don't have an extra version. The branch is called "int_module_1.0"
> and we use 1.0-SNAPSHOT on that branch. When we release, this becomes
> version 1.0 and no further work should be done on that branch. We will then
> create a new branch "int_module_1.1" and use version 1.1-SNAPSHOT there.

You can certainly have the release plugin return all the POMs to
1.0-SNAPSHOT. We use this when releasing a Release Candidate - take
the release preparation branch, release as 1.0.RC1, have it return the
POMs to 1.0-SNAPSHOT. Continue this process releasing additional RCs
until we are ready to release 1.0 proper.

You could also have it update them to 1.0.1-SNAPSHOT which is what
others seem to be suggesting. This is usually the case with my team
when we do a final release - this causes our release preparation
branch to turn into a maintenance/patches branch.

I'm not sure how to attach a branch lock to the release process but
you certainly could do so afterwards with something like 'mvn
release:prepare someplugin:lockbranch' (obviously how you do it
depends on how you lock branches in your environment).

- John

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