jira-importer commented on issue #929: URL: https://github.com/apache/maven-scm/issues/929#issuecomment-2964633667
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/Usage explains how to do that. And right now that's indeed bound to the project instead of the system. The only way I can think of is extending the `svn-settings.xml` with the option of the implementation, but that requires to manually add the maven-scm-provider-svnjava dependencies to the classpath of Maven. You probably don't want to do that for every developer. Hence, in that case define maven-scm-provider-svnjava as the svn implementation in your company-pom. As said: the out-of-the-box option is just not possible due to license issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
