Robert,
 
Try adding this to your POM:
 
<build>
  [...]
  <plugins>
    [...]
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-scm-plugin</artifactId>
      <version>1.0</version>
      <dependencies>
        <dependency>
          <groupId>com.ph.buildtools.plugins</groupId>
          <artifactId>scm-plugin</artifactId>
          <version>7.4.0.0</version>
        </dependency>
      </dependencies>
    </plugin>
    [...]
  </plugins>
  [...]
</build>
 
Also, you'll want to change your "packaging" to be "jar" instead of
"maven-plugin".  You are not actually creating a new plugin, you are
creating a new provider jar for the existing scm plugin to use.  A
related suggestion would be to change your artifact id to something like
"scm-provider-aci-custom".
 
I have created a custom provider for Serena PVCS/Changeman (my company's
SCM tool) and the "discovery" works just fine as long as you add the
dependency config for the scm plugin as shown above.  You'll also have
to similarly configure other plugins that rely on your provider
(maven-release-plugin, maven-changelog-plugin, etc.) if you use them.
 
I didn't add "DefaultScmManager.setScmProvider( String providerType,
ScmProvider provider )" anywhere in the code.
 
- Shane Genschaw


________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Saturday, October 20, 2007 9:42 AM
To: scm-dev@maven.apache.org
Subject: Re: Custom SCM Provider



All it did was change the error to: 

[INFO] [scm:validate] 
[ERROR] Validation of scm url connection (connectionUrl) failed : 
[ERROR] No such provider installed 'custom'. 

Perhaps we'd best wait for Emmanual to look at the original request.
Until then, I've trimmed the rest and proceeded onward. Once this works
I should be able to get a server connection with the code I've added
this morning. 

Thanks for the suggestions, though. 


Robert Egan 

Dennis Lundberg <[EMAIL PROTECTED]> wrote on 10/20/2007 10:16:02 AM:

> Oh, I see. I'm sure Emmanuel is correct. It might have something to do

> with naming conventions then. Just guessing here, but your 
> implementation classes all start with Custom but they implement an
"aci" 
> provider.
> 
> Dennis Lundberg

This email message and any attachments may contain confidential,
proprietary or non-public information.  The information is intended
solely for the designated recipient(s).  If an addressing or
transmission error has misdirected this email, please notify the sender
immediately and destroy this email.  Any review, dissemination, use or
reliance upon this information by unintended recipients is prohibited.
Any opinions expressed in this email are those of the author personally.


Reply via email to