Issue Type: Improvement Improvement
Affects Versions: 1.1
Assignee: Unassigned
Created: 02/Oct/12 3:37 AM
Description:

Pointers to http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/, http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/FAQ and http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/Usage would have saved me from digging around for such messages as:

{{svn: The path 'foobar' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this}}

Change the default 'svn' provider implementation to 'javasvn'

FYI: The following is also documented there so bumping the version up a notch is not be possible when thinking about backwards compatibility.
{{New work on support of svn 1.7 done (version bump to 2.0)
So version 2.0+ support only svn 1.7}}
Better approach would probably have been to force the user introduce the dependency instead of providing it as default.

<dependency>
	<groupId>com.google.code.maven-scm-provider-svnjava</groupId>
	<artifactId>maven-scm-provider-svnjava</artifactId>
	<version>2.0.3</version>
</dependency>
<dependency>
	<groupId>org.apache.maven.scm</groupId>
	<artifactId>maven-scm-provider-svn-commons</artifactId>
	<version>1.8</version>
</dependency>
<dependency>
	<groupId>org.tmatesoft.svnkit</groupId>
	<artifactId>svnkit</artifactId>
	<version>1.7.5-v1</version>
</dependency>
Project: Mojo Build Number Maven Plugin
Priority: Trivial Trivial
Reporter: Tuomas Kiviaho
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to