Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers

the file mksapi-jar-4.10.9049.jar contains some classes com/mks/api what is license for this library ? (note it contains some apache classes too : commons logging, commons-httpclient)
could it be deployed to central maven repository ?

The mksapi-jar-4.10.9049.jar can be redistributed. However, I cannot provide the sources for it.

redistributed sure.
But what is the license ?
And can you contact the owner to ask him about deploying it to central maven repo ?
see http://maven.apache.org/guides/mini/guide-central-repository-upload.html

Fixed minor issue with scm:diff

Fixed minor issue with scm:diff

Java docs for the latest source

I'm not sure what you mean by "license" for the jar. Can you explain?
I'm still waiting to hear back from the owner about deploying the jar to maven central. Couple questions:
1) Can I still proceed with this submission without the jar?
2) Is it possible to deploy the jar to maven central without sources and <scm> tags in the pom.xml?
Finally, can you remove the attachments added on 8/22? I've updated the source code to include a minor fix.

mksapi-jar-4.10.9049 has been staged: https://oss.sonatype.org/content/repositories/central_bundles-084/com/mks/api/mksapi-jar/4.10.9049/

mksapi-jar-4.10.9049 has been published to Maven Central: http://repo1.maven.org/maven2/com/mks/api/mksapi-jar/4.10.9049/
Can we move forward with the SCM Provider now?

yup I'm working on integrate it.

all committed.
I wonder if you could provide some unit tests ???
Thanks !

Sure, I can work on creating the unit tests. Any idea when maven scm 1.6 is scheduled to be released?

No idea yet for the release.
I have to review some issues first.

Attached are the unit tests that make the most sense. Some tests are intentionally excluded as some test commands execute more than one scm command (ex: login - consumed by all commands, edit - consumed by checkin, etc.). Also, I've excluded tests for CLI based commands (blame, fileinfo, and diff) as it doesn't make sense to simply assert the command line string. It almost seems like hardcoding it in two places, so theres little value. Hopefully these tests are sufficient for the intial publication/release.

Thanks !
I have excluded some by default. You can run it tru the profile tck-mks.

we are fine IMHO