[SCM-323] generateReleasePoms fails after first release:prepare

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.1
• Component/s: maven-scm-provider-perforce
• Assignee: Patrick Schneider
• Reporter: Patrick Schneider
• Created: 28/Jun/07 14:22
• Updated: 04/Jan/08 18:58
• Resolved: 28/Jun/07 15:00

Description

See line 38 of PerforceAddConsumer.

The regexp assumes a "#1" is appended to depot location when adding a file. This is only true for files that have never been in the depot before. When using generateReleasePoms, the release-pom.xml gets committed and then deleted during release:prepare. Upon subsequent prepares, the revision number will not be "#1".