Eclipse

I just ran into the following error while trying to commit (a previously working project) in Eclipse Neon:

svn: E200007: Commit failed (details follow):
svn: E200007: Commit failed (details follow):
svn: E200007: CHECKOUT can only be performed on a version resource [at this time].
svn: E175002: CHECKOUT request failed on '/svn/foo/!svn/rvr/1337/trunk/site/bar.example'
svn: E200007: Commit failed (details follow):

If you run into the following error while adding a project into Eclipse from existing source using the New Project dialog,

then you are very likely trying to create a new Eclipse project that contains Eclipse metadata files from a previous Eclipse project created at the same location. The fix for this is to import this pre-existing project into your workspace using the Import, General, Existing Projects into Workspace option.

After installing the shiny new version of Eclipse entitled 'Luna' on a Kubuntu 14.10 box, I found that it crashed/hung when trying to import/clone a Git repository. Starting the application from the command-line triggered the following notice before the crash:

When using Eclipse (Indigo) earlier today, I ran into the following error message while trying to push my commits upstream:
An internal Exception occurred during push: [URL] git-receive-pack not permitted

I'm using Eclipse (Indigo) and eGit, its Git plugin. Earlier today, when I merged the contents of one branch with my master, I ran into a bunch of conflicts. While I suspect that I should have used the "Team > Merge Tool" to resolve them, as they were rudimentary in nature, I just sorted them out manually. However, eGit did not notice that the conflicts (and their in-file markers) were gone and retained the conflicted icon for each of the affected files.

If you ever run into a git-receive-pack not permitted error when using Git, chances are that it's a configuration issue on your end. In my case, I had cloned the repository using via https (which required authentication). However, pushing failed with the aforementioned error. This was due to the fact that I was only allowed to push via SSH. Therefore, once I changed the protocol in the configuration for my checkout, all was well again.

I had to do a clean install of Eclipse today and found myself stuck with a dodgy plug-in (subversive). However, when I went to the Help menu, I did not find any option to uninstall software. IIRC, there was something along the lines of Manage configuration here where you could go to makes changes and uninstall plug-ins.

I just finished upgrading Eclipse from Galileo to the new Helios release. I performed the upgrade by adding Helios to the software sources list and updating and all seemed to go well. However, when I restarted Eclipse, I got a splash image which indicated that the upgrade had gone through and then ran into the following error message:
Failed to create the Java Virtual Machine

Shared editing is very useful for debugging / walk-throughs etc., and the Real-time shared editing plug-in, which is a part of the Eclipse communication Framework Project is nifty beyond expectations.

The following is a screencast taken from Mustafa Isik's blog:

The Eclipse 3.3.1.1 update manager has to be the most annoying updater ever fucking written. What a pile of refuse :/

I'm sure that the Eclipse developer community has their own private updater as I am certain no sane man can stand working with it.

Issues:

• If I want the update to run in the background, I should also be able to run it in the foreground.
• If I cancel the update, it should be cancelled immediately. It should not be "cancelling" for the rest of eternity and require a restart of Eclipse to get done.