[
https://jira.codehaus.org/browse/MDOCCK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MDOCCK-28.
--------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
http://maven.apache.org/ref/3.0.4/maven-model/maven.html#class_scm explains why
this is not a bug.
> unknown protocol: scm
> ---------------------
>
> Key: MDOCCK-28
> URL: https://jira.codehaus.org/browse/MDOCCK-28
> Project: Maven 2.x Documentation Checker Plugin
> Issue Type: Bug
> Reporter: Yegor Bugayenko
> Assignee: Robert Scholte
>
> This is my pom.xml:
> {noformat}
> <project>
> [...]
> <scm>
> <connection>scm:git:github.com:yegor256/jcabi.git</connection>
>
> <developerConnection>scm:git:github.com:yegor256/jcabi.git</developerConnection>
> <url>scm:git:github.com:yegor256/jcabi.git</url>
> </scm>
> </project>
> {noformat}
> This is what the plugin says:
> {noformat}
> [WARN] The scm appears to have an invalid URL
> 'scm:git:github.com:yegor256/jcabi.git/jcabi-ssl-maven-plugin'. Message:
> 'unknown protocol: scm'. Trying to access it as a file instead.
> [ERROR] The scm in file
> 'scm:git:github.com:yegor256/jcabi.git/jcabi-ssl-maven-plugin' does not exist.
> {noformat}
> Why is that? SCM format explained here:
> http://maven.apache.org/scm/scm-url-format.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira