[jira] (MRELEASE-787) release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MRELEASE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-787.
-----------------------------------

    Resolution: Fixed

I found the cause and fixed it in [r1416042|http://svn.apache.org/viewvc?rev=1416042&view=rev]
This way the release will succeed, but there's one minor afterwards: the release-pom.xml is still marked as {{added}}, since that's required for the tagging. I haven't seen the option in [SCM|http://maven.apache.org/scm] for reverting.
                
> release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)
> -------------------------------------------------------------------------
>
>                 Key: MRELEASE-787
>                 URL: https://jira.codehaus.org/browse/MRELEASE-787
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare-with-pom
>    Affects Versions: 2.2, 2.3.2
>         Environment: Subversion 1.6.12
>            Reporter: Brian Albers
>            Assignee: Robert Scholte
>             Fix For: 2.4
>
>         Attachments: MRELEASE-787.diff
>
>
> When running a prepare-with-pom goal, using the suppressCommitBeforeTag option causes the removal of the release-pom.xml to fail.
> This is due to the fact that the SVN command to remove the release-pom won't complete because the release-pom was never committed. The ultimate error is 
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare-with-pom
> (default-cli) on project com.example.project: Cannot remove release POMs from SCM
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: Use --force to override this restriction
> [ERROR] svn: 'C:\code\release-pom.xml' has local modifications
> {code}
> When suppressCommitBeforeTag is not used, the SCM operations are:
> # Status
> # Add the release-pom.xml
> # (build)
> # Commit with release version
> # Copy (create the tag)
> # Remove the release-pom.xml
> # Commit with next development version
> When suppressCommitBeforeTag is used, step #4 is omitted, which causes step #6 to fail with the supplied error. In both cases, the tag successfully has the release-pom.xml included.
> Could the --force option be used to suppress the warning?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira