checkout the maven-scm site
(http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-site/), create a
patch and attach it to a jira issue.
Emmanuel
[EMAIL PROTECTED] a écrit :
Thanks, those were the missing steps!
Question for the SCM group in general, how can I add this to the web
site before it gets forgotten? I have a JIRA account, although I've
never actually submitted any code or docs.
Robert Egan
"Genschaw, Shane" <[EMAIL PROTECTED]> wrote on 10/22/2007 11:54:32 AM:
> 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
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.
