Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8024FE481 for ; Thu, 3 Jan 2013 10:35:01 +0000 (UTC) Received: (qmail 51704 invoked by uid 500); 3 Jan 2013 10:34:59 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 51520 invoked by uid 500); 3 Jan 2013 10:34:59 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 51494 invoked by uid 99); 3 Jan 2013 10:34:58 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 10:34:58 +0000 Received: from localhost (HELO columbia) (127.0.0.1) (smtp-auth username rfscholte, mechanism login) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 10:34:57 +0000 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "Maven Users List" Subject: Re: Release preparation not removing SNAPSHOT suffix References: Date: Thu, 03 Jan 2013 11:34:52 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Robert Scholte" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.12 (Win32) See https://jira.codehaus.org/browse/MRELEASE-812 Robert Op Thu, 03 Jan 2013 08:26:30 +0100 schreef Ansgar Konermann : > Had a similar issue recently. In the directory you're trying to release, > what is the output of "git status"? > Am 03.01.2013 03:01 schrieb "Julien Silland" : > >> Hi, >> >> I'm in the process of fully automating the release of my artifacts which >> are currently checked-in an internal git repo. I've configured my >> project >> with what I think are the correct scm settings and have gotten a >> moderate >> amount of success, namely building a project and tagging a commit with >> the >> right version (foo-1.0). >> >> However, the documentation for the release:prepare phase indicates that >> the -SNAPSHOT suffix in my pom.xml should be deleted as part of the >> tagging >> process: >> >> From: >> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html >> Change the version in the POMs from x-SNAPSHOT to a new version (you >> will >> be prompted for the versions to use) >> >> But that side-effect is nowhere to be found: after the phase ends, the >> remote pom.xml hasn't been altered (it still declares 1.0-SNAPSHOT) even >> though it is tagged with foo-1.0 and the local version of the pom.xml is >> bumped to 1.1-SNAPSHOT. I would have expected a git push to happen >> before >> the tagging to change the pom.xml to a non-snapshot 1.0 version. >> Predictably, trying to perform a release builds a 1.0-SNAPSHOT jar, >> which >> is not desired. >> >> I may be expecting the wrong things to happen but would happily receive >> some guidance. >> >> My release configuration is minimal: >> >> >> org.apache.maven.plugins >> maven-release-plugin >> 2.4 >> >> Maven release plugin: >> >> >> >> >> Thanks, >> -jsi >> >> -- >> Julien Silland >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org