jira-importer commented on issue #913: URL: https://github.com/apache/maven-scm/issues/913#issuecomment-2964632684
**[Sergei S. Ivanov](https://issues.apache.org/jira/secure/[email protected])** commented SCM-772 seems to be completely unrelated to this issue. Here it looks more like `maven-release-plugin` has a bug in the sequence of the finishing operations of `prepare-with-pom` goal. I've just tried to release one of my projects, and the latest `maven-release-plugin:2.5.1` still failed miserably. The sequence of events is: 1. `git ls-files` 2. transform the `pom.xml` to the next snapshot version 3. `git rm release-pom.xml` 4. `git add \-\- pom.xml release-pom.xml` Note that `prepare` goal only executes `git add \-\- pom.xml`. At the moment the only workaround is to: 1. run `mvn release:prepare-with-pom -DpushChanges=false` (this is doomed to fail, but never mind, proceed to the next step) 2. run `mvn release:prepare -DpushChanges=false` (this will complete successfully and commit `pom.xml` changes) 3. manually amend the last commit with the deletion of `release-pom.xml` 4. push the changes into the remote repo manually 5. at this point it is safe to proceed with `release:perform` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
