[
https://issues.apache.org/jira/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961746#comment-17961746
]
ASF GitHub Bot commented on SCM-483:
------------------------------------
jira-importer commented on issue #700:
URL: https://github.com/apache/maven-scm/issues/700#issuecomment-2964613928
**[Aaron
Johnson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=swiftelan)**
commented
Because you can't just "upload it". Read:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html.
There are also other issues with the p4java implementation that may not be
acceptable to the Maven SCM project. These are listed in the "Known
Limitations" section of the p4java release notes:
http://www.perforce.com/perforce/doc.093/user/p4javanotes.txt
> Update SCM Perforce Provider to use P4Java
> ------------------------------------------
>
> Key: SCM-483
> URL: https://issues.apache.org/jira/browse/SCM-483
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-perforce
> Affects Versions: 1.2
> Reporter: Tom Rodriguez
> Assignee: Dan Tran
> Priority: Major
> Attachments: maven-scm-perforce-p4java.jar
>
>
> Perforce has developed a new Java Native API for access to perforce called
> P4Java. You can access it here:
> ftp://ftp.perforce.com/perforce/r09.1/bin.java/p4java.zip. This completely
> reworked API does not require that the p4 client be installed on the system.
> The SCM Perforce Provider should be modified to use this new native java API
> to eliminate the many issues involved with depending on the p4 executable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
