Update SCM Perforce Provider to use P4Java

I have implemented an SCM Provider using the p4java APIs. Not everything is implemented but I have been able to prepare/preform releases from Continuum and the Release Plugin.

is the p4java available in central repo ? If not it will be difficult to add this in ASF code base.
Thanks

As I know p4java not available in central repo. But why not upload it?

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

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.

If you are willing to do it, go for it. I don't have an account for that repository.

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

Actually, I had to release it so Sonatype could review it before they turn on the auto-sync to Central. Its now available at the following link before its on its way to Central.

https://oss.sonatype.org/content/groups/public/com/perforce/p4java/2009.3/

P4Java jar is now available in Maven Central: http://repo1.maven.org/maven2/com/perforce/p4java/2009.3/

<dependency>
  <groupId>com.perforce</groupId>
  <artifactId>p4java</artifactId>
  <version>2009.3</version>
</dependency>

Is there anything else that needs to be done before someone can be assigned this to work?

Aaron, I've looked a bit on your patch and I think that this patch requires a lot of refactoring.
Brian, Thank you for your effort.

I'm not an expert in the design of the Maven SCM Provider project. I still think that using the Java API that Perforce has developed is a good change for the project. What refactoring is required for this to fit into the current provider design?

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

Hi Brian,
Indeed - this is an interesting info.
BTW, do you know reasons why it can't be uploaded to Maven Central repository?

Done. Waiting for Sonatype admins to approve it and promote it to Maven Central. Should be within 24 hours.

Cool! Thank you.

Sorry for the long delay, I missed a step with releasing this. It is now available in Maven Central.

what is the license ? the pom http://repo1.maven.org/maven2/com/perforce/p4java/2011.1.297684/p4java-2011.1.297684.pom has a strange value for the licence url.

It's deployed together with the artifact (aka. the URL is relative):

http://repo1.maven.org/maven2/com/perforce/p4java/2011.1.297684/p4java-2011.1.297684-license.txt