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: local policy)
Message-ID: <493701D7.4020000@i-hicks.org>
Date: Wed, 03 Dec 2008 17:01:59 -0500
From: "David C. Hicks" <dhicks@i-hicks.org>
User-Agent: Thunderbird 2.0.0.18 (X11/20081119)
MIME-Version: 1.0
To: Maven Users List <users@maven.apache.org>
Subject: Re: Limitation of the release plugin?
References: 
 <DE36A88276CCF042AC2721634CB35746072B60D3@zcarhxm2.corp.nortel.com>
In-Reply-To: 
 <DE36A88276CCF042AC2721634CB35746072B60D3@zcarhxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Never noticed or thought about it.  On my team, we call a "cease fire" 
when a build is being done to avoid any such problems.  We were doing 
that before using Maven, too, so it's a bit of a hold-over.  I can see 
your point, though.


Todd Thiessen wrote:
> I have been looking at the release plugin a fair bit lately and noticed
> something that concerned me.
>
> The first modification of the pom changes the version to remove the
> "-SNAPSHOT" and also changes the SCM values to point to the tag location
> instead of the trunk location.  Once done, it then commits this change
> to trunk.
>
> So what happens if another user checks out the project during this
> window?  I just tried testing it myself by interrupting a
> release:prepare right after the first commit.  I then checkout the
> project to a another directory and lo and behold, the version looked
> like a released version and the SCM information referenced the tag not
> the trunk.
>
> Can anyone else confirm this? This seems pretty dangerous.
>
> ---
> Todd Thiessen
>
>
>   

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