Hi,
Have you try adding scm (svn) dependencies to the site plugin declaration ?
btw please load an issue we could add this in the site plugin pom.
Thanks,
--
Olivier
2010/9/17 Andrew Phillips :
> Hi
>
> The following is about a potential issue with the maven-site-plugin-3.x
> branch.
> I'm not sure if this is the most appropriate forum but I hope someone will be
> able to point me in the right direction, e.g. by suggesting to turn this into
> a
> JIRA issue.
>
> The question is: does the 3.x branch of the Maven site plugin support site
> URLs
> that use one of the SVN SCM wagons? I know the documentation
> (https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-3.x/src/main/java/org/apache/maven/plugins/site/SiteDeployMojo.java)
> still states
>
> that officially only scp and file are supported, but I know it also works with
> dav and svn so I'm assuming it could potentially work with all wagons.
> The issue I am facing is the following: if I try to run mvn site:deploy -X
> with
> a site URL of
>
> scm:svn:https://...
>
> I see the following in the output:
>
> [DEBUG] The site will be deployed to url 'scm:svn:https://...' with id
> 'some-site-site'
> [DEBUG] repository protocol scm
> [DEBUG] getProxy 'protocol' : scm
> [DEBUG] getProxy 'protocol' : scm no ProxyInfo found
> [DEBUG] found proxyInfo null
> [DEBUG] authenticationInfo with id 'some-site-site' : null
> [WARNING] No SCM providers configured.
> [DEBUG] configureWagon
> ...
> [DEBUG] configureWagon server sonatype-nexus-staging
> [DEBUG] connect with authenticationInfo and without proxyInfo
> scm:svn:https://... - Session: Opened
> ...
> Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException: No
> such
> provider: 'svn'.
> ...
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading
> site
> at
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:271)
> ...
> Caused by: org.apache.maven.wagon.TransferFailedException: Error interacting
> with SCM: No such provider: 'svn'.
> ...
> at
> org.apache.maven.wagon.providers.scm.ScmWagon.putDirectory(ScmWagon.java:510)
> at
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:257)
> ... 21 more
> Caused by: org.apache.maven.scm.manager.NoSuchScmProviderException: No such
> provider: 'svn'.
> at
> org.apache.maven.scm.manager.AbstractScmManager.getProviderByType(AbstractScmManager.java:155)
>
>
> Looking at the output, it seems that SCM is not picking up any of the
> registered
>
> SCM providers, even though the POM contains
>
>
> org.apache.maven.wagon
> wagon-scm
> 1.0-beta-6
>
>
> org.apache.maven.scm
> maven-scm-manager-plexus
> 1.3
>
>
> org.apache.maven.scm
> maven-scm-provider-svnexe
> 1.4
>
>
> I've also tried making these dependencies of the SCM and site plugins but that
> doesn't make any difference, neither does setting
> true
> on the plugins.
>
> In any case, I'm not sure if I should need these providers at all, because if
> I
> just run scm:status I can deal with an scm:svn connection and
> developerConnection even if the extensions aren't listed in the POM.
>
> One thing I did notice: the site plugin's POM
> (https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-3.x/pom.xml)
> contains dependencies on
>
> (amongst others) the webdav wagon, but not on any SVN SCM providers. Might
> this
> be the reason..?
>
> Thanks in advance!
>
>
> Andrew Phillips
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
