I am working on a C++ project using Eclipse Kepler V4.3.1 with the CDT plugins on Fedora. Up until yesterday, everything seemed to be working fine, but now when I make a change Intellisense/Content Assist doesn't seem to see it. (Note that this is not the same problem with getting autocomplete to make suggestions that I have seen others post about.)
For example, if Eclipse picks up on an error like passing an invalid argument to a function, when I then go and fix the error Eclipse continues to complain about it. It continues to show me the old line before I made the change. If I open that same file with Emacs or gedit, I see that in fact the change was made and saved.
Here is what I have tried without success:
Right click on the project > Index > Rebuild
Right click on the project > Index > Freshen All Files
Right click on the project > Index > Update with Modifies Files
Restarting Eclipse
Restarting the entire machine
Checking for software updates and installing them (plus restarting).
Any ideas?
For others who might run into this issue, I wish I had a better solution but here is what solved it:
Delete the entire build directory
Clean the project
Delete the files I had been working on and re-add them.
Right click on the project > Index > Rebuild
Restart Eclipse
I'm not sure which part actually did it since I had also previously installed updates, but things seem to be working again.
Related
I use eclipse Indigo, subclipse 1.10.x and javaNL. Whenever I try to refresh my project in eclipse, it gets stuck at Reverting Resources 0% and Computing Update Requirements 0%. I try to kill eclipse and reopen the project and it still does the same. I do not understand why this happens. It started happening recently. Before it was working fine.
Question: I do not understand why this happens
General Answer: http://www.ihateeclipse.com/
(I may share this opinions and dont think Eclipse should be called a IDE but that wont fix your problem - hence lets proceed with possible workarounds).
Possible Workarounds:
1.) Starting eclipse in clean mode How to run eclipse in clean mode? and what happens if we do so?. (This solved aprox. 80% of my continuously returning 'I messed up my own state' issues I experienced).
2.) If that doesnt help - you would have to stop eclipse, identify the according files (or just any files holding such information) and delete them manually, then restart eclipse. Like I still encounter issues with my "Search Type" (Ctrl+T) and have to delete the files like described here Eclipse type hierarchy not always working (unfortunately I don't know anything about files regarding your current issue - so feel free to downvote my "answer" since its not directly answering your question).
The best things I found about "the full reset" seem to be: http://letsgetdugg.com/2009/04/19/recovering-a-corrupt-eclipse-workspace/ or http://blog.pdark.de/2011/09/02/restoring-a-corrupted-workspace-in-eclipse/ (Note: I haven't verified the described behaviors).
3.) Recreate Workspace - delete any eclipse belongings like the .metadata folder and keep only belongings of your project (e.g. sources, resources etc.). Then create a new eclipse project based on you existing project sources).
4.) If Steps 1-3 failed consider reinstalling Eclipse (include above Step 3 in this process again) or switching to a proper IDE that can at least handle its own state.
5.) I experienced rare cases where in the end such things were triggered by me rather than occurred magically out of nowhere by eclipse - I don't see any possibility on how you could manage that in your case unless you messed around with the eclipse source itself).
Hope this helps - Even thus the SO community is big I experienced way better results asking the eclipse developer community directly when it came to such specific issues (you however oftenly get a link to a open Bug ... that they created because of your question) and ended up "just importing into a new eclipse workspace from existing sources" whenever I experienced such issues lately (It takes me about 5 minutes to checkout our sources, start Eclipse with -clean as default and import existing Maven projects solving any eclipse-only issue - while each of those eclipse-issues can take days to be solved without any further advantage for my daily business)
I don't know if this will help any one but I had the same issue. Some links advised me to delete my metadata, which I did not want to do.
What fixed it for me was:
I have multiple eclipse workspaces, I manually closed my eclipse using the System Monitor/Taskbar as it wouldn't let me close as it was hanging.
I switched workspaces and it seems to run fine. So I switched back to the one that was hanging and the problem seemed to have gone.
This worked for me:
Go to to your workspace instalation, and manually delete the target directory under your maven projects (dont worry , maven will create another one when compiling). This removed my stuck Eclipse state (thread) in "Revert sources", always at 0%.
this helped me:
delete files "*.snap" under org.eclipse.core.resources in
worskpace/.metadata/.plugins/org.eclipse.core.resources/
and share project again (setup SVN settings)
I accidentally checked in target files to SVN. And the target files were huge ans hence it was stuck on reverting resources. Once I deleted those target files from SVN this issue never happened.But JBA's answer is pretty comprehensive so I will mark that as a right answer.
I have this same issue, and I just quickly cancel the "Rerverting Resources" task while it's in "waiting" mode when restart Eclipse.
This should work to 100% and helped in my case (no other tried solution worked):
Go to "Eclipse > Help > About Eclipse IDE > Installation Details
Uninstall the following packages "Subclipse", "Subclipse Integration for Mylyn", "Subversion 1.14 JavaHL", "Subversion Revision Graph", "SVN Client Adapter".
pluginsToUninstall
Go to the marketplace and install "subclipse" again.
Rightclick on your project > Team > Refresh/Cleanup
You are welcome. :)
I am running Windows XP and Eclipse 4.2.2 Build id: M20130204-1200 and I have lost my Debug and Launch tool bars. I have tried Windows>Reset Perspective (original values) and Window>Customize Perspective's (Tool Bar Visibility and Command Groups Availability) tab options. I have tried the Layout option on Debug view. All failed to bring them back. Right now, I am looking at Tool Bar Visibility tab and a message that says: <"Debug" cannot be made available because it is in the unavailable "null" command group.> However, the Debug checkbox in Command Group Availability is checked.
I have also tried right-click and Reset on the perspective buttons.
Switching to another eclipse installation (same machine) did not help either.
Rebooting does not help.
Are there any text configuration files where this data is stored that can be manipulated outside eclipse?
I had this problem in Eclipse Kepler, it turns out it was caused by PyDev plugin. I fixed it by uninstalling the plugin and right-clicking on the Debug perspective button and selecting Reset.
I had already installed a fresh copy and the problems persisted. But, encouraged by user714965 comments, I tried again but that did not resolve the issue. Then, I threw away all eclipse installation folders (to recycle bin), re-installed fresh copy, and the problem persisted. Then I started a new workspace, and it seemed like the tool bars were back. Then restored previous eclipse installations and they had the Debug toolbar as well!
I am thinking somehow the customization config files were broken. It would be nice to know where the these files are stored (my original question): Are they global for each user on the machine or are they workspace specific? It seems to me that some customizations are global, while others are project specific.
May be it is time to try the new Android Studio :-)
Seems as your eclipse is broken. The fastest way to get it back running will be downloading a fresh copy from eclipse.org. You can continue using your current workspace so your settings will remain. But you have to re-install all plug-ins... I'm always keeping a backup of a fresh release with the plug-ins I'm using. I would suggest you to do the same in the future.
Update 28 May 2013:
I have found a work around for this. Though this is not always works MOST of the time it does.
In Eclipse > Preferences > General > Startup and Shutdown
uncheck the option "ClearCase Remote Client plug-in"
Every time I start the problem workspace, before doing anything (like click on any resource or click on project in project explorer) I connect to the ClearCase repository.
This seems to calm down the error most of the time. Also, the Eclipse shortcut that I have on my desktop, has -clean option set in it. So when I start the eclipse my eclipse already starts with the clean up option. Though not sure if it has any bearing on the problem.
However not sure if this will help in a situation when I am working offline; when I can not connect to the ClearCase repository.
Update 21 May 2013:
At this time it looks like there is no resolution for this except a CCRC plugin upgrade.
For now marking VonC's answer as correct. Will update the post if I find a better solution.
I created a fresh new workspace and setup the workspace and so far I do not see any problems so far. Still not sure what was wrong with my workspace though.
==================================================
I have been having this problem for quite sometime on one of the workspace.
Error:
I am seeing the following error pop up with the error message; and will NOT go away.
An error has occurred. See error log for more details.
Could not initialize class com.ibm.rational.team.client.ui.model.common.ImageManager
Symptoms:
It happens only in one work space almost all the time.
Every time I restart this workspace, when ever I click on any projects in project explorer or any open file, it causes the error pop up to come up.
It goes away if I close all files, close the offending project and then delete the project. I fire up eclipse, re-import the project and the issue goes away only as long as I continue using the eclipse. Once I restart the eclipse the same problem persists.
What I have tried so far:
start eclipse with -clean option --> It does not solve the problem.
I have enabled the "Refresh workspace on startup" option in "Eclipse > Preferences > General > Startup and Shutdown" --> this does not solve theproblem.
I deleted the folder "org.eclipse.core.resources" under "Offending_Workspace > .metadata > .plugins" folder --> this has no effect. The problem persists as mentioned in Symptoms3 above.
System Info:
Windows 7 Enterprise Edition 64 bit.
Eclipse 3.7 Java EE developers
CCRC plugin Version: 7.1.0.0 , Build id: 7.1.1.03.00_2010C.D100803
Is there anything that can be done to resolve this. It's frustrating to work with such a broken plugin, that practically hinders ones work.
Any suggestion will be helpful.
This looks like PM38965 and there is no other solution than upgrading:
A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5 and 8.0.0.1
You can see it listed in this release note:
PM38965:
Addresses a ClearCase issue where the ClearTeam Explorer produces a "Could not initialize class com.ibm.rational.team.client.ui.model.common.ImageManager" error intermittently when performing various operations.
The OP reports a workaround:
In Eclipse > Preferences > General > Startup and Shutdown, uncheck the option "ClearCase Remote Client plug-in"
Every time I start the problem workspace, before doing anything (like click on any resource or click on project in project explorer) I connect to the ClearCase repository.
This seems to calm down the error most of the time.
Also, the Eclipse shortcut that I have on my desktop, has '-clean' option set in it. So when I start the eclipse my eclipse already starts with the clean up option.
Though not sure if it has any bearing on the problem. However not sure if this will help in a situation when I am working offline; when I can not connect to the ClearCase repository.
The '-clean' being a local operation, it will have the same effect offline or online.
I launched Eclipse earlier to jot down a snippet and was faced with the following as an error when I tried to run a fresh project:
An internal error occurred during: "Compute launch button tooltip".
That popup window shows as soon as I mouse-over the run icon in the top bar, or if I right click on the class in the explorer window and select any of the run/debug options.
After doing some research on the error, I see several people who posted similar messages but they all have been fresh installs of Eclipse. So note that this is not a fresh install, and that Eclipse was working fine earlier today. Also note that not only does my new project not run (with the normal main method), but projects I was running earlier have all stopped working with the same error.
Finally, also be aware that after seeing other people's suggestions on fixing this, one specifically said to select run configurations from the top of the page run menu. When I selected run configurations from this dropdown, I got the following message:
Exception occurred creating launch configuration tabs
Reason: Plug-in org.eclipse.jdt.debug.ui was unable to load class org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup
After that message, the run window opens but all of the tabs are missing. Like where you can set the display width and height, and the other tabs, they are all missing from the window now.
I was using Eclipse trouble free earlier today and I am sure no updates took place between when Eclipse was working and now. My question is of multiple parts: What is wrong in a nutshell? What could have caused this?
Got this from another site of some guy who got this same error after upgrading.
Worked for me as well.
Apparently putting the following line in your eclipse.ini helps:
-Dcom.ibm.icu.util.TimeZone.DefaultTimeZoneType=ICU
Try setting the launch properties in:
Window>Preferences>Run/Debug(Expand)>Launching(Click)
Under launch Operations menu set it to:
Always launch the previously launched application
Click:
Apply>Ok
I never found out what went wrong, but a reinstall of eclipse fixed it. All projects survived seemingly undamaged.
Thanks for the reply on the .ini but that did no good.
I had same error today - in an eclipse installation (Juno SR2 64bit) that has been running fine for months.
0: There were no changes on svn for my projects since yesterday (when it was running fine).
1: I restored the workspace from a 'Windows 7 -> Properties -> previous copy' backup. This failed because the directory structure of the '.metadata' contains folders with a deeper structure than is supported.
2: I restored the workspace from a overnight archive (gzipped so file depth is not an issue).
This had no effect.
3: I tried to restore the eclipse installation directory (which seems to be updated an awful lot) from a 'Windows 7 -> Properties -> previous copy' backup. Again this failed - because of folder-depth issues (Note: it is installed in the root directory of my disk - so there is actually no way to use a restore on this installation!)
4: Had to delete the .metadata from my workspace and reinstall eclipse (and all the additional plugins), and re-import my projects, and setup all the servers, and android, etc, which took many hours.
The moral of the story? Backup both your workspace AND the eclipse installation every night manually. Windows Restore will NOT save you. Backing up your workspace is NOT enough.
I had the same problem using eclipse mars. I cleared the folder .recommenders\index
And that solved my issue.
Hope it helps.
incase you are having the eclipse files which you have downloaded from the official site .Just extract those file in the same folder where your previous eclipse was installed and select replace all.
best solution
I also encountered this issue, the reason why this issue occurred on my project was due to I was missing the JRE System Library in the root folder of my project.
To solve this issue, make sure you have the libraries like JRE System Libraries on the root folder of your project.
While compiling an android project in eclipse 3.4.2, I am getting The project cannot be built until the build path errors are resolved.
I got a temporary solution from the blog http://www.scottdstrader.com/blog/ether_archives/000921.html
The resolution was to force a resave of the selected projects (and their .classpath files):
Open the project properties
Select Java Build Path > Libraries
Add a new, arbitrary library (to be deleted later) > OK
Wait for the workspace to refresh (or force a refresh of the project)
The error(s) will go away
Remove the dummy library
The only other references I could find were to make minor alterations of contents of the .classpath file.
Is there any permanent fix for this issue?
Have you tried using Project > Clean... from the menu? This will force a new build on the selected projects in Eclipse.
1-Right CLick on your project folder, Choose Build Path > Configure Build Path
2-Select Libraries Tab and delete any arbitrary library present there.
3-Click on Add Library option, Select JRE System Library and click Next.
4-Choose last Radiobutton option Workspace default JRE and click Finish.
5-press f5 for refresh.
6-run ur program .
This what fixed it for me...
I was having an issue with my spring-core.jar.
I deleted the entire release directory located here. (I'm on win 10).
C:\Users********.m2\repository\org\springframework\spring-core\4.3.1.RELEASE
I right clicked on the project > Maven > Update project and my exclamation mark disappeared. No problems any more.
Here is the source where I found the information:
http://crunchify.com/cannot-be-read-or-is-not-a-valid-zip-file-how-to-fix-maven-build-path-error-with-corrupted-jar-file/
This happens when libraries added to the project doesn't have the correct path.
Right click on your project (from package explorer)
Got build path -> configure build path
Select the libraries tab
Fix the path error (give the correct path) by editing jars or classes at fault
This works for me: close the project then re-open it, this will force eclipse to reload a fresh project and detects the correct build path.
None of the other answers worked for me. Even after fixing my build path issues, doing a refresh, clean, rebuild, and restart (of both eclipse and the computer), I was still getting the little red exclamation point.
I fixed it by closing the project (right-click, close project) and reopening it (double-click the closed project), which seemed to force eclipse to "notice" that the build path problems had been corrected.
For my mac osx Eclipse, I followed following steps:
Right CLick on your project, Choose Build Path > Configure Build Path
Select Libraries Tab and delete any arbitrary library or anything else causing errors in Build Path.
Click on Add Library button, Select JRE System Library and click Next.
Choose last Radiobutton option Workspace default JRE and click Finish.
Clean and build your project.
get a cmd and run
mvn eclipse:eclipse
This is what worked for me:
Go to ~/.m2/repository and deleted everything there by running rm
-rf. Make sure everything is deleted.
Re-launch eclipse or STS
Right click on project -> Maven -> update project.
On my Mac this is what worked for me
Project > Clean (errors and warnings will remain or increase after this)
Close Eclipse
Reopen Eclipse (errors show momentarily and then disappear, warnings remain)
You are good to go and can now run your project
I've seen this problem a few times (got it again right now on my home computer with Eclipse 4.2).
Forcing a resave (by changing the classpath e.g. by adding a library, save, change-back) works temporarily. But the problem comes back when Eclipse is restarted :(
Nuking the Eclipse workspace from orbit will permanently fix it (until next time). But there must be a better way!
just check if any unnecessary Jars are added in your library or not. if yes, then simply remove that jars from your library and clean your project once. Its worked for me.
In Eclipse this worked for me: right click project. -> Properties -> Library Section; Add (any library at all) -> select library and click remove -> press okay.
I ran into this annoying issue with the Play framework. It would be nice if there was some way of knowing what build errors Eclipse is unhappy about, but it's not going to tell you. With one project, I was able to close the project, rebuild the Eclipse configuration with sbt eclipse, and reopen. With an almost identical project, that didn't work. But deleting the project, rebuilding the Eclipse configuration with sbt eclipse, and importing, did the trick.
If you think you've done everything correctly but Eclipse still complains about the jars, refresh the folder where the jars are and make sure eclipse knows they've been added to the project. Specifying the file path alone is (apparently) not enough
I've faced this issue a couple of times and following the below steps has resolved both the times.
1. Navigate to C:\Users\
2. locate the ".m2" folder and delete it.
Now navigate to the particular project in eclipse and Right-click on the project > Maven > Update Project
wait until the project is updated and in my case following the above steps resolved both the times.
I was getting an additional warning
The compiler compliance specified is 1.6 but a JRE 1.8 is used
Resolving this warning make the error also go away. The steps are as follows:
I right-clicked on it, then clicked on Quick Fix. From the dialog that opened I selected Open the Compiler Compliance property page, and clicked the Finish button.
(This is same as Java Compiler section.)
In this dialog I found the Compiler compliance level drop down and changed 1.6 to 1.8, and clicked on Apply and close.
I got a message box Compiler Settings Changed which asked if I wanted to Build the project now?. I clicked on Yes.
The build path error went away.
Go to > Right CLick on your project folder > Build Path > Configure Build Path > Libraries Tab > remove project and external dependencies > apply & close
Now, Gradle refresh your project.
Added below to pom.xml file and it worked eventually:
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>4.0.0</version>
<scope>provided</scope>
</dependency>
Goto to Project=>Build Automatically . Make sure it is ticked