Description
When performing a release after a branch-dry-run, the temp file 'pom.xml.branch' should be ignored. Now the perform will fail, because the working copy has modifications.
There has been an issue that was closed as "Won't fix": MRELEASE-425
Information about the patch:
Based on r983489 in https://svn.apache.org/repos/asf/maven/release/trunk
Online Compare View: http://github.com/lcorneliussen/maven-release/compare/473197249e1caf39ee2cee6d0efc8a288c30d0c3...939d6e05bbed440622a40b2094e31963d0a90c78
Included commits:
MRELEASE-425Fixed: When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run (by Lars Corneliussen<me@lcorneliussen.de> on 05.05.2010 17:01:54)
Attachments
Attachments
Issue Links
- is duplicated by
-
MRELEASE-425 When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run
- Closed