[
http://jira.codehaus.org/browse/SCM-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SCM-323:
-----------------------------
Fix Version/s: (was: 1.x)
1.1
> generateReleasePoms fails after first release:prepare
> -----------------------------------------------------
>
> Key: SCM-323
> URL: http://jira.codehaus.org/browse/SCM-323
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0
> Reporter: Patrick Schneider
> Assignee: Patrick Schneider
> Fix For: 1.1
>
>
> 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".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
