Eclipse oxygen hangs on every git operation - windows

I had a work-blocking problem with my Eclipse Oxygen IDE on Windows 10. After using SVN for several months I switched to a project that requires git usage. I already had the necessary plugin (EGit) in place.
After every git-related operation the Eclipse froze: team->share, import -> Projects from Git etc.
I tried the following:
reinstall the EGit plugin,
clean the workspace I was using
start over with the new, clean workspace
but nothing helped...

It finally turned out it was the fault of my git installation on windows!
I was using version 2.6.x, because I wasn't using git for a long time due to SVN projects. After upgrading windows installation to 2.16.x Eclipse freezes no longer happen.

Related

Wakanda v11's git extension install broke Wakanda v10's git functionality

I have both v11 and v10 Enterprise Studio/Server installed on my Mac. When I launched v11 for the first time, I installed the Git extension through the extension manager. This broke Git in v10.
Launching v10, right-clicking a file, and opening a solution in v10 gives the below errors.
Git options are now grayed out in the Studio v10 Git menu. I've uninstalled v10 and reinstalled it, and uninstalled Git 2.6.4 and reinstalled it to no avail.
Git works fine in v11 but I'm not ready to make the switch because my application does not run in v11.
Git is installed to /usr/local/bin/git, but is there another directory that would hold Git or Wakanda-Git configuration files?
I am thinking I need to blow away whatever changes Wakanda Studio v11's extension manager made to my Wakanda/Git setup to fix Git in v10.
Remove the git folder inside your documents/Wakanda/extensions/ and restart Wakanda Studio 10 I think it should fix it.

Why is git slow on my windows machine?

Just typing git at the command prompt (of powershell), takes 2.5 seconds until it returns with the help message.
I'm using the git for windows release, installed in C:\Program Files (x86)\Git. When I use cygwin (via babun), I get an error: Hint: your prompt is very slow. Check the installed 'BLODA' software. Maybe this is related? If it is, I'm using a corporate laptop, so can't uninstall antivirus or driver software, are there other options?
For me the reason seemed to be the "Inject ConEmuHk" setting in cmder under which I ran git. I've opened a bug https://github.com/bliker/cmder/issues/592
Try and see if the issue persists with the latest 2.4+ git for Windows release.
There is a bug related to the git bash startup time which is actively addressed.

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 :)

SVN version in Maven tasks with SVNKit on 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.

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.

Resources