[
https://issues.apache.org/jira/browse/SCM-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960504#comment-17960504
]
ASF GitHub Bot commented on SCM-110:
------------------------------------
jira-importer commented on issue #421:
URL: https://github.com/apache/maven-scm/issues/421#issuecomment-2964593401
**[Jeff
Jensen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jeffjensen)**
commented
Would you mind explaining further please? mvn clean does not delete
"source" files, only target files, so am wondering your premise.
The only time I can think of needing a force sync is when the use says to do
a "full get latest", which in Perforce terms means to get it all again, even
though I probably already have it. For those in CVS land, this is cvs co vs
cvs update.
When does your change make this happen? The code change was in the checkout
source file, so only on checkouts, or do other actions reuse this code?
> 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)
