[
http://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231274#action_231274
]
Brian Jackson commented on SCM-483:
-----------------------------------
I've got the p4java jar staged. Aaron can you take a look and sanity check
that everything is in order before I release it to Central?
https://oss.sonatype.org/content/repositories/comperforce-362/
Since its closed source, but the sources jar is a requirement, I've staged an
empty sources jar on purpose. I spoke with Jason van Zyl and he state that as
long as the license allows for redistribution of binaries then its not a
problem.
The conversation ended here:
http://twitter.com/jaxzin/status/20516410745
> Update SCM Perforce Provider to use P4Java
> ------------------------------------------
>
> Key: SCM-483
> URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
