Home/ Questions/Q 6981309
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T18:08:25+00:00

I’m having some problem with Maven’s scm element and subversion. I added the following

  • 0

I’m having some problem with Maven’s scm element and subversion.

I added the following to my pom.xml:

<scm>
  <connection>scm:svn:svn+ssh://user@x.y.z/repositorypath</connection
  <developerConnection>scm:svn:svn+ssh://user@x.y.z/repositorypath</developerConnection>
  <url>scm:svn:svn+ssh://user@x.y.z/repositorypath</url>
</scm>

in order to use svn revision in my JAR files manifest.

But when I run “clean package” on that, I get this:

[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: The path 'C:\xxxxxx' appears to be part of a Subversion 1.7 or greater
working copy.  Please upgrade your Subversion client to use this
working copy.

Still, subversion seems to work great otherwise: I can checkout, update and commit just fine from Eclipse. I also tried running upgrade for my working copy, but it was already upgraded.

Our subversion server is 1.6.11 and my Eclipse uses Subclipse 1.8. Java HL is 1.7.2

So what should I change to get this to work? Also, is there a way to omit the username from the svn+ssh url? So that the pom.xml could be use by all developers?

EDIT:
I should have mentioned that I also added buildnumber-maven-plugin to my pom.xml when I started getting this error. I now looks to me as if that plugin is unable to deal with my subversion version. Oddly it’s homepage here claims that the newest is 1.1-SNAPSHOT, while I can’t find newer than 1.0 (must I enable using snapshots explicitly somehow?)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have used the scm element correctly in your pom.xml

    One way to avoid having to handle username/password is to configure an anonymous read-only access to your repository to be used for build and similar purposes. Otherwise, the SO references alluded to above gives some directions on how to externalize at least the password, if not the username.

    As for the error message, you see this because of difference in the versions of the subversion client used by Eclipse and maven scm plugin.

    From the error message, it looks like Eclipse has created (some of) the subversion folders (.svn) in the newer (1.7) format. It looks like maven scm client uses the 1.6 format as per this.

    One way to fix the problem is checkout the project using maven scm plugin itself or an older subversion client.

    • 0