maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien Silland <julien.sill...@turn.com>
Subject Re: Release preparation not removing SNAPSHOT suffix
Date Fri, 04 Jan 2013 20:00:40 GMT
Thanks for the pointer to the bug. I've configured my project to use the 2.3.2 version of the
release plugin and things are working as expected. I haven't explored switching to different
scm version dependency.

-- 
Julien Silland


On Thursday, January 3, 2013 at 2:34 AM, Robert Scholte wrote:

> See https://jira.codehaus.org/browse/MRELEASE-812
> 
> Robert
> 
> Op Thu, 03 Jan 2013 08:26:30 +0100 schreef Ansgar Konermann 
> <ansgar.konermann@googlemail.com (mailto:ansgar.konermann@googlemail.com)>:
> > 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" <julien.silland@turn.com (mailto:julien.silland@turn.com)>:
> > 
> > > 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:
> > > 
> > > <plugin>
> > > <groupId>org.apache.maven.plugins</groupId>
> > > <artifactId>maven-release-plugin</artifactId>
> > > <version>2.4</version>
> > > <configuration>
> > > <scmCommentPrefix>Maven release plugin: </scmCommentPrefix>
> > > </configuration>
> > > </plugin>
> > > 
> > > 
> > > Thanks,
> > > -jsi
> > > 
> > > --
> > > Julien Silland
> > > 
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org (mailto:users-unsubscribe@maven.apache.org)
> For additional commands, e-mail: users-help@maven.apache.org (mailto:users-help@maven.apache.org)
> 
> 



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message