You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Jackson (JIRA)" <ji...@codehaus.org> on 2011/09/29 15:47:17 UTC

[jira] Commented: (SCM-483) Update SCM Perforce Provider to use P4Java

    [ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280252#comment-280252 ] 

Brian Jackson commented on SCM-483:
-----------------------------------

I've just found out that Perforce has implemented a Maven SCM provider for Perforce on top of their p4java API.  But they only offer it as a download you need to manually install into your own Maven repository.

http://www.perforce.com/perforce/doc.current/manuals/p4maven/index.html

> Update SCM Perforce Provider to use P4Java
> ------------------------------------------
>
>                 Key: SCM-483
>                 URL: https://jira.codehaus.org/browse/SCM-483
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.2
>            Reporter: Tom Rodriguez
>             Fix For: future
>
>         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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira