Subversion command line client version is too old (1.6.11) After updating to IDEA 2018
Answered
Seeing these messages after updating to 2018.
Can't use Subversion command line client: svn
Subversion command line client version is too old (1.6.11). Fix it.
Previously the native client was unticked but this checkbox is missing in IDEA 2018? has svnkit support been removed?
svn 1.6 is part of the toolkit I'm using so I need to maintain the current svn client and side install a newer version manually for IDEA? how do I do that?
The 'fix it' link isn't helpful at all, offers no fix whatsoever, what version of svn do I need? 1.6.11 is the latest on this VM CentOS 6.8 and I can't update the distro, its a client image. What can I do? go back to IDEA 2017 then I'm wasting my continued IDEA subscriptions?
Please sign in to leave a comment.
Yes, SVNkit has been removed - see https://blog.jetbrains.com/idea/2018/01/2018-1-changes-to-subversion-integration/
You need svn client 1.7 or above. Actually, you should be able to install any client, including 1.10, as they are backward compatible with1.6 servers.
If for some reasons you need to use 1.6. and upgrade does not work, comment on https://youtrack.jetbrains.com/issue/IDEA-184261 and describe the reason, but so far all users who came to support were able to install new client locally and successfully use it.
The products I'm working on with this VM are also integrated heavily with subversion, but only the base 1.6 version, only supports 1.6 working formats and the client needs to match. So I can't update the default OS level subversion client. Can I install a later version of subversion somewhere else and not have the interfere with each other?
You can, of course, install several command line svn clients on the system, and use a newer one without updating the system-level client. You could even use a portable version. But working copy format has to match the client version, unfortunately. So it will be not possible to use two different clients on the same working copy.
You could do a separate checkout though, with the newer working copy format, and use it in the IDE, leaving the 1.6 working copy like some kind of a mirror, if needed.
But I can't use any rpms as they'll probally upgrade the existing subversion rather than side install a new version that's not the default. Can't seem to find any info on how to go about this. Guessing compile subversion from source? But what changes to make?
Compiling from sources is always an option, especially for linux.
But you could try using some kind of portable clients, or supplied as tar.gz.
Probably this page can help https://subversion.apache.org/packages.html
Link only seems to suggest rpms - I'll see it I can find some compatible portable clients. But I suspect most portable clients will be for Windows only.
BTW, SVNkit is still available in 2017.3 and earlier, so if no other options found, you could keep using that version while working on old RedHat.
Thats where I can in and it's what I'm going to have to do. Couldn't find any subversion client .zip, .tar.gz binaries for Linux no portable version either.