You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2014/06/26 07:15:10 UTC

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

     [ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Tran closed SCM-483.
------------------------

    Resolution: Won't Fix
      Assignee: Dan Tran

maven scm provider for Perforce using p4java is not at workshop.perforce.com

> 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
>            Assignee: Dan Tran
>             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 was sent by Atlassian JIRA
(v6.1.6#6162)