[
https://issues.apache.org/jira/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961744#comment-17961744
]
ASF GitHub Bot commented on SCM-483:
------------------------------------
jira-importer commented on issue #700:
URL: https://github.com/apache/maven-scm/issues/700#issuecomment-2964613932
**[Brian
Jackson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jaxzin)**
commented
Aaron, the Sonatype guys have simplified the process of getting artifacts
into Central and Tim O'Brien wrote a great post on the process:
http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/
I'll be glad to take the time to follow this post to get p4java in Central,
unless you want to do it.
> 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)
