Hi Cletus! There is not much difference between a 3rd party maven-scm and the internal ones. The main difference is that the dependencies for the maven-release-plugin and other core maven-plugins will already contain the 'internal' maven-scm providers as dependency.
But you can easily add your own provider to the maven-release-plugin and maven-scm-plugin too. Just add a <dependency> for it. The scm-provider itself get's picked up via the plexus-role (e.g. 'git', 'svn', 'cvs, 'jgit', etc). Just use that in your <developerConnection>. Do you have to code to share somewhere? If so, then I might take a look. What SCM is that for? LieGrue, strub --- On Sun, 8/14/11, Cletus D'Souza <[email protected]> wrote: > From: Cletus D'Souza <[email protected]> > Subject: RE: Noob Questions - New SCM Provider > To: [email protected] > Date: Sunday, August 14, 2011, 1:49 AM > > Update.... > > So, looks like I was able to figure out the magic with the > pom.xml and get a successful compile and > package/install. Also was successful with some > connectivity tests going from the SCM provider code to > Integrity. > > The only question I now have is how can I package up an > external (propriteary) jar file as part of the provider > jar? Right now I've installed the mksapi.jar using > "mvn install:install-file..." to my local repository. > Is this the only way? > > Finally, once I'm done with this provider would it be > possible to make it available to download directly from > maven? > > Thanks! > Cletus > > > > > From: [email protected] > To: [email protected] > Subject: Noob Questions - New SCM Provider > Date: Sat, 13 Aug 2011 00:02:30 -0400 > > > > > > Hi All, > > I'm hoping someone could answer some of these basic > questions with regards to writing a new SCM provider for > Maven. > 1) What is the version for <version>LATEST VERSION OF > MAVEN-SCM PROVIDERS MASTER POM</version>? I'm > guessing 1.5? > 2) I created a basic shell class by extending > AbstractScmProvider. However, when I compile I get the > following error: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-plugin-plugin:2.7:descriptor > (default-descriptor) on project > maven-scm-provider-integrity: Error extracting plugin > descriptor: 'No mojo definitions were found for plugin: > org.apache.maven.scm:maven-scm-provider-integrity.' > 3) Also, I keep seeing these errors in Eclipse using the > Maven integration. Can these be ignored? > > 8/13/11 12:00:29 AM EDT: Configurator > 'org.maven.ide.eclipse.modello.modelloConfigurator' is not > available for project 'MavenPlugin'. To enable full > functionality, install the configurator and run > Maven->Update Project Configuration.8/13/11 12:00:29 AM > EDT: Configurator > 'org.maven.ide.eclipse.plexus.annotations.plexusConfigurator' > is not available for project 'MavenPlugin'. To enable full > functionality, install the configurator and run > Maven->Update Project Configuration. > > Thanks! > Cletus > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
