SVN version in Maven tasks with SVNKit on MacOS - macos

I am getting this error in a Maven build (mvn clean install) on a Mac with Mountain Lion
org.tmatesoft.svn.core.SVNException: svn: The path 'XYZ' appears to be part of Subversion 1.7 (SVNKit 1.4) or greater
working copy rooted at '/Users/XYZ/workspace/XYZ'.
Please upgrade your Subversion (SVNKit) client to use this working copy.
I had SVN installed as part of the Apple Command Line tools package and that gets installed at /usr/bin. I have installed the latest SVN as well but that got installed at /usr/local/bin.
When the maven build runs, it does not pick up the latest SVN, it picks the older one and fails.
Has anyone faced this kind of problem before?
I think there are 2 options -
1) Somehow force maven to use the new installed SVN.
2) Upgrade the SVN installed as part of Apple' Command Line tools to the latest SVN. I have reinstalled Command Line tools with the latest version but it still sticks to the older version.
I dont control the pom.xml so modifying it is not a viable option.
Any pointers in resolving this would be much appreciated.
Thanks!

This means your svn client is version 1.7 but the working copy(your project workspace) was checkout with the older version.
It's simple by execute the following command at your project root directory, where the pom.xml is there.
svn upgrade
please note, the maven use the svn client which is in your OS path.
After upgrade you should configure your IDE to use the version 1.7 as well. In my case I use the Eclipes Juno sr1 with Svnkit.
Anyhow if you would not like to change the working copy or IDE configuration. There is an alternative by install the svn clinet 1.4/1.5/1.6 and set it active via OS path instead.
I hope this may help.
Regards,
Charlee Ch.

Related

Upgrade Maven Version in Windows

I want to upgrade to Maven latest version from 3.2.2v in windows. I know that there is a command as I used it before, but unable to recollect it now and haven't found in google even after an hour. So, can some one please help me with the command.
Thanks,
Likitha
Maven has no command to upgrade to Maven 3.X. You should download and extract new version.

How to use existing SBT installation instead of downloading a new one in intelij?

I'm using os x and I've installed sbt with brew. After I've installed intellij and scala plugin for intellij it recognized .scala files of my project and suggested to import sbt project. When importing I saw that intellij is downloading sbt instead of using sbt installation that I have installed previously. How to force intellij to use sbt from brew? I don't want to clutter my ssd...
It is not a wise decision. sbt API changes slightly between versions. If intellij requires certain version for inner processing, it would be better to fulfil its expectations.
Set sbt.version in project/build.properties. IntelliJ respects the requested version. It won't download again if it has already been downloaded. You probably see this because the launcher you installed is a different version than what is installed in intellij. You can also set intellij to use the launcher you already have installed by changing the setting in preferences

svn: E155021: This client is too old to work with the working copy at xxx (format '31')

I am trying to import some gradle projects in my Spring Tool Suite . I have installed Subclipse 1.10.5 in my STS and svn client installed in my machine is 1.8.8 . I have tried downgrading to 1.7.10 on my mac but still I get the same problem while importing .
For others SVN 1.7.10 and Subclipse 1.10.5 seems to work fine but in my machine I am getting the error
svn: E155021: This client is too old to work with the working copy at
'/Users/agarg/Documents/Mars/trunk' (format '31')
Stuck here for some time now and unable to resolve this . Tried a lot of things as I found over the net but still stuck.
I had this problem on Mac OS Yosemite with Webstorm and IntelliJ.
svn --version on the command line printed 1.8, but even with command line client option enabled with value svn in Webstorm/IntelliJ I was getting the warning.
Running which svn and pasting the value (/usr/local/bin/svn for me) into WebStorm->Preferences->Version Control->Subversion->Use command line client removed the warning and fixed the issues I was having in Webstorm and IntelliJ.
The working copy has format understandable by SVN 1.8 client, but your client is SVN 1.7 or older.
You should double-check what Subclipse / SVNKit / svn.exe client versions you have on your system.
Try accessing the working copy from command-line and see whether you get the same error.
If you definitely have svn installed and running at the correct version you want, this error means the metadata in your project refers to an older version of subversion. Upgrade it by following this guide: http://www.robsearles.com/2008/12/svn-client-is-too-old-to-work-with-working-copy-solution-using-rsync/
I had this same issue on OSX. I have been able to upgrade the SVN by following the step by step guide here:
URL: http://andowebsit.es/blog/noteslog.com/post/how-to-upgrade-subversion-on-osx/
First check which svn version you have:
$ svn --version
svn, version 1.7.17 (r1591372)
compiled Aug 7 2014, 17:03:25
...
Seems like its old version, so update it.
$ brew update
$ brew install subversion
This will take some seconds to install. Now check how many svn you have. You will see the another entry belew.
$ which -a svn
/usr/bin/svn
/usr/local/bin/svn
Edit the ~/.bash_profile with
export PATH="/usr/local/bin:$PATH"
And then
$ source ~/.bash_profile
$ svn --version
svn, version 1.8.10 (r1615264)
compiled Aug 25 2014, 10:57:58 on x86_64-apple-darwin13.3.0
...
Now you will see the SVN verison is upgraded from 1.7 to 1.8.
Same problem here (SVN 1.8 client on W7, STS 3.6.3, eclipse-plugin: subversive SVN Team provider 1.1.x and SVNKit Implementation 3.0.x).
Upgrading (in STS) the SVN Team provider to 2.03.x and SVNKit to 4.1.2 solved the problem.
Got this error ON MAC OS X but you believe you have available the right version?
First look at how many svn
$ which -a svn
/usr/local/bin/svn
/usr/bin/svn
/usr/local/bin/svn
Look at the output for each of the output using the --version flag. You might notice that the default which output is not the same as the default command output:
$ command -v svn
/usr/bin/svn
$ which svn
/usr/local/bin/svn
You might be tempted to update some symlinks or your PATH variable but before doing so try from a new console, it might be just that you are hitting a console open before you installed the latest version. I would even try restarting before attempting to change PATH or symlinks.
Easiest way:
1. execute which -a svn in terminal;
2. modify the enviroment file(like ~/.bash_profile), and use the older version svn;
3. checkout svn code with your older svn;
4. import it into your IDE;
5. DONE.
I had similar issue in my program while checking out code from SVN through my Java program .
TO resolve i closed the eclipse workspace and deleted the folder in which i was checking out the files on my local directory.It worked for me.
Thanks to all for their solution. I was struggling with this issue for couple of days. I had installed old version 1.7 with PC login of Cygwin environment.
Later i had to install version 1.9 because i wanted to use svn command. For most of the time i was looking for a file /.bash_profile on my PC or file which would have path usr/local/bin.
But i always found path cygwin/usr/local/bin. I kept neglecting it.
After doing so many trial and error, i took simple chance.
Went to Environment Variable PATH, and cut path "C:\Program Files\TortoiseSVN\bin\bin" and pasted before "cygwin/usr/local/bin"
And later svn --version detected my latest version 1.9 :)

Eclipse SVN plugin install fail on mac pro

Yesterday I had install the eclipse and the Android plugin. Everything works perfectly, but I would like to install the SVN plugin too. I had add the suite, and selected the three main components, but when I click on the next it stack in. The eclipse write "Calculateing requriements and dependencies" and than I just waiting.
So I had disabled all another update site and it works, but then I got the following message:
"could not upgrade:missing compnents: svn.rep.grap". It is very good, but I would like to install this component at NOW beside of the another svn tools.
Any ideas?
The Subclipse plugin can be installed from the Eclipse Marketplace Client or by adding the update site URL of http://subclipse.tigris.org/update_1.8.x
Note that Subclipse requires the JavaHL native library that is part of Subversion. The easiest way to get this is to install the latest Subversion client distribution provided by CollabNet:
http://www.open.collab.net/downloads/community/
You can also install Subversion via MacPorts. Both of these include the JavaHL library and properly link it in your System folder so that is visible to the Subclipse plugin running in Eclipse. I would assume you could also install via Homebrew but I have not tried that option.

Installing Subversion on top of already installed Apache?

I have a working WAMP environment (Apache Friends). I decided to try Subversion and downloaded CollabNetSubversion-server-1.6.9-1.win32.exe. On the download page there were packages including Apache server which I did not use - because I didn't want to replace my current Apache installation.
I just installed the one that did not include Apache, and now I want to configure it to work with my current Apache. What should I do?
Is there an easy step by step tutorial to explain this?
There's lots of tutorials such as the XAMPP (apache friends) version http://serk01.wordpress.com/2008/09/21/how-to-create-your-own-home-svn-repository-with-xamppapache/ and the WAMP version http://www.reloadedpc.com/other/setup-wamp-svn-subversion-windows/
If all you want to do is create a repository and do checkins and updates locally on your windows machine then just install TortoiseSVN. Tortoisesvn only installs the shell extension for windows explorer, not any command line svn executables. To get those you have to download them separately and make sure they're the same version of svn that tortoise uses or you'll get errors about version mismatches when using the command line svn.

Resources