Hello Stefan! Yeah, I knew, that the release is based on the working copy, which have to be "clean". We've had a bugusing the release plugin (look at http://jira.codehaus.org/browse/SCM-406) On http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.htmlthere is a "remoteTagging" parrameter to solve this bug if you are using SVN > 1.5. But I have not found what is "remoteTagging" doing. This bug should be fixed in the release plugin 2.0-beta-9, we're using 2.0-beta-8. Our workaround was to make an "svn update" before doing a release:perform. Thank you very much Stefan! I hope you're fine ;-) -Danny Schimke
2009/7/21 Stefan Hübner <[email protected]> > Hi Danny, > > you're probably talking about the maven-release-plugin, right? what do > you mean by "remote tagging" specifically? > > During prepare the plugin forces the user to have a clean working > copy, i.e. no uncommited changes. If the working copy is clean, it > modifies POM by increasing version numbers and altering SCM-connection > URLs, it then commits those changes and tags them. > > During perform the plugin checks out that newly created tag to a > temporary working folder and performs the actual release step on that. > > Hope that helps? > > -Stefan > > 2009/7/16 Danny Schimke <[email protected]>: > > Does remote- Tagging meant, that the (SVN-) Trunk- version is used for > > prepare / perform the release instead of using the local workingcopy? Is > > that correct? > > > > Thank you! > > -Danny Schimke > > > > -- > > Danny Schimke > > IT- Consultant > > > > incowia GmbH > > > > Albert-Einstein-Straße 3 > > D-98693 Ilmenau > > www.incowia.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Danny Schimke IT- Consultant incowia GmbH Albert-Einstein-Straße 3 D-98693 Ilmenau www.incowia.com
