You should have to do one of the following:
- add the dependency on the new provider to the maven-scm-plugin pom.xml
- in your pom, add it as part of the scm plugin declaration:
<plugin>
<artifactId>maven-scm-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-new-scm-provider</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
We're working on a solution to this need for Maven 2.1.
what is the new provider? Will it be contributed to the project?
- Brett
Mcmahon, Chris wrote:
> I've implemented a new SCM provider, and everything seems to be in order, but
> I can't get the SCM plugin to recognize it at runtime. I can compile and
> install the new provider as an artifact locally. I've got the right
> information set in the src\main\resources\META-INF\plexus\components.xml
> file.
>
> As a sanity check, I took the source for an existing SCM provider and copied
> it, altering the POM accordingly, renaming all the packages, altering
> ScmProvider's getScmType() method to return the new provider key, and altered
> the plexus\components.xml to point to the provider with the proper key.
> Again, I was able to compile and install, but the provider is still not
> recognized.
>
> -- Is it a requirement that SCM implementations be child modules of the
> scm-providers project or can they be independent projects?
> -- Should I be editing existing SCM POMs in my local repository to reference
> the new implementations?
>
> Any help would be appreciated
>
