I just happened to disable Maven Nature. Now to re-enable it again I was trying to do Right Click Project: Configure > Convert To Maven Project.
However I do not see Configure option anymore. How do I convert it back to maven project again? I deleted the project and re-checked it back from the truck but to no avail!
Never mind, I fixed the problem just by restarting eclipse. Looks like lot of inconsistencies arise if you operate Eclipse for too long. I guess its good practice to save work and restart eclipse every now and then.
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 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.
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've just installed Eclipse Juno with m2e installed.
Then, I've created a new Maven project and decided I want log4j, so I opened the pom.xml, clicked on the Dependency tab, clicked on the Add... button and typed in log4j.
Zero results. The only thing that it finds is junit (that was automatically added to the project with the quickstart archetype, it seems). Note that I can add the log4j dependency manually and it will work just fine, but I find the search feature really convenient!
I'm a kind of a Maven beginner, though I got m2e working no problem in Indigo. So I'm thinking I might have forgot to set something?
All you have to do is update or rebuild your workspace maven repository index.
Open your "Maven Repositories" view. Open Global Repositories and right-click on central. Enable full index and rebuild.
Initially the process will take several minutes. After that your search will start working.
You can automate this process by turning Download repository index updates on startup on in your workspace preferences under Maven
in case rebuilding your workspace maven repository index didn't work, try reinstalling m2e. I updated mine via marketplace and it started working again. I'm not sure what was the issue but I suspect some URLs got changed recently.
Just go to Window -> Preferences -> Maven
and check the option Download repository index updates on startup and click Apply. That's all.
What is the advantage with not having a build path in eclipse? Why is that setting default when it's like something you'd never use? It seems eclipse indigo was developed to make software development as obscure as possible. I just checked out a fresh copy of the project I checked in (called dungeonworld) this afternoon from another computer and automatically nothing works, can't compile, can't choose build path, can't add jre, can't add jdk, can't add that to project properties.
Is my eclipse broken? I can't believe this is happening, such an easy thing not feasible.
Nothing above solutions worked for me so i tried below
Right click on project >> properties >> project facets >> click on java
It looks like you did not add Eclipse project metadata files to your source control system, so Eclipse doesn't know what your build path is or whether it is even a java project. You can see that the little folder on your dungeonworld project is missing the little 'j', which means Eclipse doesn't think it's a java project.
Go back to your other computer and look for the following files in your original project root...
.project
.classpath
.settings/*
Make sure all of the end up in your source control system or nothing will work right.
I have same problem, but i have solved
project right click -> properties -> java build path -> src/main/sources
all remove items on "Excluded", and then that item turn the status "(None)"
I tried below steps and it works for me.
Right click on project >> properties >> project facets >> click on java
Eclipse has a build path.
It's stored in a (by default hidden) .classpath file in your project.
You can also access it through the UI in project properties (right click on your project, properties, java build path).
Well, this is probably not your problem, but similar is happening if you are in Eclipse different perspective (for example for Python).
vs.
There where no entrys after right click on my projekt in Eclipse. How to click something, wenn build path entries are missing. So my Eclpise didn't detect my java project. I used following Maven command and after that I cleaned the project too. Now Projekt works as expected. So...
If you are using Maven, try mvn eclipse:eclipse in cmd console in your project directory! Make sure to use the path to your Maven folder for the command.
For example:
cd C:\yourEclipseProject\
C:\yourPathToMaven\apache-maven-2.2.1\bin\mvn eclipse:eclipse
This was helping me. After unsuccessful web research, a coworker told me this tip.
I just had a similar problem and I figured out that I had been choosing General Project instead of Java Project while creating a project. After I chose Java>Project it solved my problem. Maybe it'll solve yours as well.
After choosing that, eclipse automatically included java libraries as well.
It's not a good practice to commit IDE related files into source control. What if someone in team uses different IDE? It might have been only option at a time when OP asked this question.
New versions on eclipse (4.x) takes care of this automatically. Probably by observing what kind of source and build files you have in your project.
Don't know the reason. But this works for me, so posting it.
Right click on project -> 'Properties' -> 'Java Build Path'.