[
https://issues.apache.org/jira/browse/SCM-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961894#comment-17961894
]
ASF GitHub Bot commented on SCM-524:
------------------------------------
jira-importer commented on issue #735:
URL: https://github.com/apache/maven-scm/issues/735#issuecomment-2964615688
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Syncing with an none-existing label / daterange / client causes the
> PerforceCheckoutCommand to report success
> -------------------------------------------------------------------------------------------------------------
>
> Key: SCM-524
> URL: https://issues.apache.org/jira/browse/SCM-524
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.2
> Reporter: Erlend Hamnaberg
> Priority: Major
> Attachments: PerforceCheckoutStdErr.patch
>
>
> Perforce reports errors in stdErr, not stdout.
> Meaning if you try to
> p4 sync ...@none-existing-label
> you will get the
> Invalid changelist/client/label/date '@none-existing-label'. in stderr.
> See attached patch to address this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
