[
https://issues.apache.org/jira/browse/SCM-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960506#comment-17960506
]
ASF GitHub Bot commented on SCM-110:
------------------------------------
jira-importer commented on issue #421:
URL: https://github.com/apache/maven-scm/issues/421#issuecomment-2964593404
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
If you do a release:perform, maven checks out the tagged source code to
target/checkout and builds that to generate the official released binaries. If
for some reason you need to perform a release twice (maybe because it failed
the first time) and had run 'mvn clean' between attempts, target/checkout would
be gone but the p4 sync would not know that...
> Perforce should force sync
> --------------------------
>
> Key: SCM-110
> URL: https://issues.apache.org/jira/browse/SCM-110
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Reporter: Mike Perham
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-3
>
> Attachments: force2.txt
>
>
> It's not pretty but it's the only way to get sync to work when files could be
> deleted from the filesystem (e.g. mvn clean).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
