Eclipse stuck while building project, "-clean" does not work - eclipse

My eclipse gets stuck when I try building a project, usually at 80%. I also get a heap error, even though I already increased it to 750mb and the same project previously worked with 350mb.
I tried starting up eclipse with the "-clean" command, but according to the log it's not effective:
!MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: C:\Program Files\eclipse\configuration\org.eclipse.osgi
Edit:
Okay, the build error seems to be caused by faulty libraries. And -clean did not work because I was starting eclipse without administrator rights (Windows 7).

As stated in the Edit:
The build error seems to be caused by faulty libraries. And -clean did not work because I was starting eclipse without administrator rights (Windows 7).

I had this problem also and it happend after I updated a Jar file.
Turns out the jar I had added was compiled with the wrong version of java.

Related

Can only use PyDev plugin when running Eclipse as root or using -clean option

Overview
I am running Ubuntu 15.10 with Eclipse Mars 4.5.2 (from the Oomph installer) and and Java 1.8 and Python 2.7. I am attempting to the PyDev 5.2.0 plugin for Eclipse. Installing with Eclipse's update manager seemed to go okay. The only problem is that I can only see PyDev related options when I run Eclipse with sudo.
What I have tried
I made sure to set the java VM path in the eclipse.ini file so the Eclipse binary runs with Java 8.
I added Java 8 to Eclipse's JREs and set to be default.
I tried running the Eclipse binary with the -clean option.
The first two didn't allow me access to the PyDev options in Eclipse. Running as a normal user with the -clean option did let me see the PyDev options, but running as a normal user without -clean made the PyDev menu options invisible again.
Finally, I noticed that running Eclipse as root made the PyDev options appear again. This suggested that there was some ownership or permission problem. Since my Eclipse installation and plugins are in my home directory, I made sure my user has ownership over everything in the home directory. I also reviewed the permissions of files related to the PyDev plugin, and it appears I have the appropriate permissions, but since I do not know which permissions each file ought to have, I am not sure.
I am not sure what is going on. It is especially surprising given that I was able to install the CDT plugin not long ago without any hassle. It's also possible the problem might be related to how root's environment is configured compared to my user's, but being able to access PyDev when running with -clean seems to vanquish that theory.
I could just run Eclipse as root from now on, which isn't that big of a deal. However, it is quite annoying not knowing why this is happening, making me feel like I don't have control over Ubuntu and Eclipse.
My guess is that you have the eclipse configuration folder not accessible by the current user (or some other folder inside the .metadata).
Try verifying/fixing the permissions on those folders (I don't exactly know where those folders go on the default ubuntu install, but on windows it's eclipse/configuration and the .metadata is where you point your workspace to).
In my case, upgrading to Ubuntu 16.04 solved my problem. After the upgrade, PyDev was working normally in Eclipse.

Eclipse - An error has occured. See the log file null

I know this issue was posted like a thousand time. However, non of them seem to solve my issue.
When trying to open Eclipse, whether by clicking the on .exe or thru cmd with -clean command, I receive "An error has occured. See the log file null.".
So as mentioned in the other post, I deleted the .snap file or the workbench folder or the whole .metadata folder and yet, the error pops up. So I deleted Eclipse and downlaoded the Eclipse Installer .. and surprise .. same error.
Since I deleted Eclipse I do not have any log I'd know of.
Hope one of you, have a guidance for me, that would be great. :)
Thanks
Well I was facing the same problem probably because I had multiple JVM versions installed in my machine. I fixed the problem by specifying the exact JVM I wanted eclipse to use in the eclipse.ini file.
-vm
C:\Program Files\Java\jdk1.8.0_11\bin
So I was using Eclipse Mars 2 32-bit at C:\Program Files\eclpise\ on Windows 7 with Java 1.8.0_91 32-bit as well. Don't know why, but I ended up deleting Java and reinstalling it and it worked.
#E-Riz, thanks for you're help anyway :)
In my circumstance, I ask my friend about java version (java -version in windows terminal). All you need is reinstall Java as his recommendation.
(My java: java 1.8.0_161 Java SE and my Eclipse is Java EE 64 bit)

UnsatisfiedLinkError Starting JVM Via Eclipse

I have a plain Eclipse installation without much of anything, and a workspace with a Maven (or better yet Tycho) project. Everything worked until I decided to change the JDK (Preferences -> Installed JREs); now whenever I start a Maven build or the plug-in unit tests I get the following error:
Error occurred during initialization of VM
java.lang.UnsatisfiedLinkError: java.lang.Class.getClassLoader0()Ljava/lang/ClassLoader;
<<no stack trace available>>
I have restarted Eclipse and tried a different installation, and since I thought the problem was with the JRE, I changed it back to the original one. Still the same error.
The corresponding 64bit JRE works, but sadly the build has an integration test for 32bit (Cannot load 32-bit SWT libraries on 64-bit JVM), so that's why I need to get 32bit to work again.
How do I fix it?
Deleting all the .metadata folder of the workspace and setting it up again helped.

Trouble launching Eclipse Juno

This is silly, but I am running out of ideas.
I downloaded the latest eclipse (EE) 64 bit package for my mac, untarred it and upon launching it, got an error message. Reopening it, of course did not work.
I tried:
Rebooting
Downloading package from multiple mirrors
Downloading non-EE version fails with same error
Downloading Indigo version - starts up and runs fine.
I have already installed:
Standard Juno installed (non EE). It can run without any issues. Could there be a conflict with anything here?
New non-EE version Juno install fails with the same error as EE version
I am not sure what else to try or how this behavior can be explained. Any ideas?
I am running on 10.8.2 OSX (Mountain Lion) with security settings enabled to
The problem was the Unarchiver. As part of untarring, it corrupted something.
Once tarball was untarred manually, everything worked like a charm. No magic.
I had the same trouble in the same situation.
After the latest update eclipse.ini file was lost in Eclipse.app/Contents/MacOS folder.
I recovered it and restarted eclipse(eclipse -clean). Successfully it started working.
I just ran into the same problem, took forever to figure it out because I just updated eclipse.ini then it was gone again after an update.
A recent bug about Eclipse Update removing the eclipse.ini in Mac OS X (Sept 29, 2012)
"Bug 390756 - Juno SR1 update is removing the eclipse.ini file"
https://bugs.eclipse.org/bugs/show_bug.cgi?id=390756#c40
See comment: David Williams 2012-10-10 16:15:52 EDT:
Starting fresh from SR0 or SR1 works fine, but starting with the already
broken version (even with eclipse.ini restored) does indeed delete the
eclipse.ini.

Subversive not showing up in eclipse

I am trying to install subversive for eclipse helios on windows 7. I am seeing it as installed in the installation details, but it is not showing up as a perspective and also in windows/preferences/team. Can anyone help me with this.
I fixed that issue by granting my user writing access to the eclipse installation directory (default in "Program Files" is read access).
#squig - +1
changing the directory permissions (I placed it under c:\program files\eclipse in Windows 7) caused the subversive plugin to work, after spending endless hours on trying to figure out the issue.
The lame part from Eclipse side (or Subversive side, dunno) is that no error message was shown, it appeared as if the software was installed properly. Shame.
I had exactly the same problem. But in my case the problem could not be solved be granting write access to the eclipse programm directory.
The reason was that I tried to use two versions (Mars and Neon.2) of eclipse in parallel. When I tried to install both programms into one directory in "C:\Programm Files (x86)\Eclipse" it was not possible to install plugins etc. to the newer version. Therefore I uninstalled the newer version and reinstalled it under "C:\Programm Files (x86)\Eclipse-Neon".
After this everything is fine. Even without write permissions to the programm directory.