[
https://issues.apache.org/jira/browse/SCM-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961337#comment-17961337
]
ASF GitHub Bot commented on SCM-414:
------------------------------------
jira-importer commented on issue #625:
URL: https://github.com/apache/maven-scm/issues/625#issuecomment-2964607453
**[Peter
Janes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterj)**
commented
The previous patch touched more files than necessary. I've reduced it to
only the single needed file.
Both cases can appear, depending on whether the "p4 sync" command has an
argument or not:
$ p4 sync
File(s) up-to-date.
$ p4 sync ...
... - file(s) up-to-date.
> Patch Submisson Fix Maven Perforce SCM Plugin so that it will work with
> Continuum
> ---------------------------------------------------------------------------------
>
> Key: SCM-414
> URL: https://issues.apache.org/jira/browse/SCM-414
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.1
> Environment: Tested on linux should work on any platform.
> Reporter: David Trott
> Priority: Major
> Attachments: perforce.diff, scm-414.patch
>
>
> There are a couple of issues with picking up the perforce password.
> - Added code to pick it up from the standard environment (P4PASSWD) if not
> set elsewhere.
> - Changed the DataOutputStream to a OutputStreamWriter as the
> DataOutputStream throws in extra unicode characters
> The "file(s) up-to-date" message has a different case F on different
> platforms.
> Omitted it the F from the string compare.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
