[
https://issues.apache.org/jira/browse/SCM-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960505#comment-17960505
]
ASF GitHub Bot commented on SCM-110:
------------------------------------
jira-importer commented on issue #421:
URL: https://github.com/apache/maven-scm/issues/421#issuecomment-2964593407
**[Jeff
Jensen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jeffjensen)**
commented
Thanks for explaining.
So this -f occurs only in the release:perform, or elsewhere too?
If not only with release:perforce, that is ugly; highly inefficient. It
takes us about 20 minutes to get a full one. Instead of hardcoding that (in
effect, saying -f needs doing for all use cases), would it work to param it
somehow, e.g. command line, property, etc. so that the nasty duration only
occurs for those that need it?
> 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)
