Re: Release Plugin Failing on Commit
On 09/04/2010 12:16 AM, Neil Chaudhuri wrote: I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://SVN IP/data/svn/client/myapp/tags/myapp-1.1.rc4' does not exist in revision 5218 Have you correctly configured scm tag in your pom.xml before releasing? I have seen similar errors when I had mistake in developerConnection tag. Martin Schayna - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release Plugin Failing on Commit
What is your svn version ? Aren't you facing to this bug : http://jira.codehaus.org/browse/MRELEASE-375 Using the option remoteTaggingtrue/remoteTagging should slve it. (It is weird but I was sure we had a note somewhere about this annoying issue we had a long time ago, but I didn't find it) cheers Arnaud On Sep 4, 2010, at 12:16 AM, Neil Chaudhuri wrote: I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://SVN IP/data/svn/client/myapp/tags/myapp-1.1.rc4' does not exist in revision 5218 To be fair, that's true--myapp-1.1.rc4 isn't a folder in the SVN tags folder. But I figured the plugin would create it and put my source code underneath. Another weird thing is that the poms are updated to 1.1.rc4 and committed to the trunk and checked out to my local machine. The expected behavior is for 1.1.rc5-SNAPSHOT to be in the trunk and on my local while the 1.1.rc4 is in the tagged version. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0/version configuration updateWorkingCopyVersionsfalse/updateWorkingCopyVersions preparationGoalsclean install/preparationGoals goalsclean install/goals arguments-Dmaven.test.skip/arguments tagBasesvn://SVN IP/data/svn/client/myapp/tags /tagBase autoVersionSubmodulestrue/autoVersionSubmodules /configuration /plugin Any advice on how to get the expected behavior is appreciated. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release Plugin Failing on Commit
On 2010-09-04 00:16, Neil Chaudhuri wrote: I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://SVN IP/data/svn/client/myapp/tags/myapp-1.1.rc4' does not exist in revision 5218 To be fair, that's true--myapp-1.1.rc4 isn't a folder in the SVN tags folder. But I figured the plugin would create it and put my source code underneath. Another weird thing is that the poms are updated to 1.1.rc4 and committed to the trunk and checked out to my local machine. The expected behavior is for 1.1.rc5-SNAPSHOT to be in the trunk and on my local while the 1.1.rc4 is in the tagged version. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0/version configuration updateWorkingCopyVersionsfalse/updateWorkingCopyVersions preparationGoalsclean install/preparationGoals goalsclean install/goals arguments-Dmaven.test.skip/arguments tagBasesvn://SVN IP/data/svn/client/myapp/tags /tagBase autoVersionSubmodulestrue/autoVersionSubmodules /configuration /plugin Any advice on how to get the expected behavior is appreciated. updateWorkingCopyVersions is only available in the branch goal. Are you trying to release from a branch? If so then by using updateWorkingCopyVersions=false you have told the plugin that you don't want it to update the version in your working copy. Thanks. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release Plugin Failing on Commit
I get that error all too often, as well. I haven't found a solution for it. On Sat, Sep 4, 2010 at 3:35 PM, Dennis Lundberg denn...@apache.org wrote: On 2010-09-04 00:16, Neil Chaudhuri wrote: I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://SVN IP/data/svn/client/myapp/tags/myapp-1.1.rc4' does not exist in revision 5218 To be fair, that's true--myapp-1.1.rc4 isn't a folder in the SVN tags folder. But I figured the plugin would create it and put my source code underneath. Another weird thing is that the poms are updated to 1.1.rc4 and committed to the trunk and checked out to my local machine. The expected behavior is for 1.1.rc5-SNAPSHOT to be in the trunk and on my local while the 1.1.rc4 is in the tagged version. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0/version configuration updateWorkingCopyVersionsfalse/updateWorkingCopyVersions preparationGoalsclean install/preparationGoals goalsclean install/goals arguments-Dmaven.test.skip/arguments tagBasesvn://SVN IP/data/svn/client/myapp/tags /tagBase autoVersionSubmodulestrue/autoVersionSubmodules /configuration /plugin Any advice on how to get the expected behavior is appreciated. updateWorkingCopyVersions is only available in the branch goal. Are you trying to release from a branch? If so then by using updateWorkingCopyVersions=false you have told the plugin that you don't want it to update the version in your working copy. Thanks. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release Plugin Failing on Commit
I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://SVN IP/data/svn/client/myapp/tags/myapp-1.1.rc4' does not exist in revision 5218 To be fair, that's true--myapp-1.1.rc4 isn't a folder in the SVN tags folder. But I figured the plugin would create it and put my source code underneath. Another weird thing is that the poms are updated to 1.1.rc4 and committed to the trunk and checked out to my local machine. The expected behavior is for 1.1.rc5-SNAPSHOT to be in the trunk and on my local while the 1.1.rc4 is in the tagged version. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0/version configuration updateWorkingCopyVersionsfalse/updateWorkingCopyVersions preparationGoalsclean install/preparationGoals goalsclean install/goals arguments-Dmaven.test.skip/arguments tagBasesvn://SVN IP/data/svn/client/myapp/tags /tagBase autoVersionSubmodulestrue/autoVersionSubmodules /configuration /plugin Any advice on how to get the expected behavior is appreciated. Thanks.
Re: Release Plugin Failing on Commit
On Fri, Sep 3, 2010 at 6:16 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: What command did you execute? What does the scm section of the pom look like? Also, it looks like there is a trailing space in your tagBase element, which might be causing trouble. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
