I installed following plugins in eclipse indigo in following order to start spring development
Spring Tools Suite
M2E (Maven)
after these two installations, it was giving error
jira connector not installed, so I installed the following plugin.
Atlassian Jira Connector
After installing Jira Connector, Eclipse Started showing the following error :
Uninstalled Jira Connector. Still Showing these Problems.
Any help would be appreciated.
Eclipse has major structural problems with uninstalls, which aren't really fixed even the latest luna. But don't worry, there are a lot of workarounds.
What you can do now and in similar situations:
1.
If you can even uninstall something, you won't get back its previous state before the install.
Because of it I use Eclipse normally with a trick: I store my main Eclipse install directory in a git repository, and so I can always switch back with a single command. But it is only a trick.
2.
There is a big chance, that only your workspace directory is damaged, and not your Eclipse. In this case you can solve this problem by reinitializing your workspace: make a backup, delete everything, recreate your workspace directory and finally import again your projects.
(For similar reasons it is also an useful trick to save your workspace metadata in a git repository as well.)
3.
In Eclipse, the menu items are created by modules. If an eclipse module is installed, it creates the changes in its internal configurations which create the menu items.
After a restart, Eclipse tries to restore your gui, and thus re-open its panels. But if a module uninstall is also happened, then its panels aren't restorable, resulting exactly your problem.
So, simply close the bad panels and try to reopen them. Sometimes it also works.
In short: recreate your workspace, it will probably help. And next time, use Eclipse with some good and frequent backup (I suggest git).
Related
I'm new to GIT and recently moved over one of my eclipse java projects.
I noticed a significant delay in the auto build of my project after moving it to GIT. Seems to be some GIT update that happens on every save.
"Updating GIT status for repository GIT"
I'd appreciate any insights.
Eclipse version: Luna RC3 Release (4.4.0RC3)
I'm not sure if this is the culprit but almost every time in the last couple of Eclipse releases I have had issues with the Remote System Explorer which often for some reason gets called when you have source control plugins or aspectj on a project.
For a git project on Luna I turned it off by following:
"Remote System Explorer Operation" causing freeze for couple of seconds
Yes the answer is for a different problem but again I have found the Remote System Explorer to be the culprit (or maybe indirectly I don't know for sure but I do know when I turn it off things get faster). There is also some git specific answers to that referenced SO question but I found I had to turn RSE completely off.
I have recently had a problem with Eclipse. I am developing a java application. It suddenly freezes whenever I try to save a file. Indeed, it happens to some files in my project while it works fine with the others. I have checked the .log file in my workspace and there is no error message! I tried to disconnect my project from GIT, but the problem persisted. It drives me crazy. I have to restart Eclipse many times everyday.
Any solution would be greatly appreciated.
Such kind of issues should provide all related info: OS, Java, Eclipse version, list of plugins installed. Example of file saved. CPU, RAM size, memory setting for Eclipse.
Without knowing those details some recommendation would be to analyze and try to find the cause by comparing:
try on other PC,
with other Java version
other Eclipse version
the same Eclipse version without any additional plugins.
increase Eclipse memory settings
Check if it is build related by disabling automatic build.
Check if there are "Save Action" configured in Preferences.
and so on.
maybe some plugin causes that, but usually people just go with new Eclipse instance instead of comparing different plugins combinations.
See also How can you speed up Eclipse?
Eventually, it's worked. I created a new workspace and import it my project to it. Everything works well since then, like a magic! It seems the problem occurred because my workspace was too old. I have been working on the same workspace since more than 2 years.
Thanks fellows for your time to help.
While developing Nodeclipse, I found that some bugs don't arise immediately but after some time, when combination of updates, restarts happens.
Is plugin update or uninstall/install really clean?
I develop and use installing for update, then use newer version until I got time/idea to improve. However as said above I ran into situation when Eclipse behaves differently after the new feature have been used for several days.
Is there some information that must be read about plugin install life-cycle, that mentions some not so evident behavior.
UPDATE: Some problem were in Autumn 2013 when we were switching to tycho build. Also around that time Eclipse Kepler 4.3.1 was released.
No, they are not "clean". Moreover when you do uninstall, no files are deleted, Eclipse would just prevent plugin from loading on the startup.
If you really want to remove the plugin you need to
Uninstall it via UI
Delete the plugin files in the file system
Remove plugin settings from workspace or create a new one.
Here is some interesting info for you:
There is no mechanism within Eclipse to permanently and physically
uninstall a feature and its plug-ins. The process to physically and
permanently remove an undesirable feature and its plug-ins is a manual
process that should be done when Eclipse is not running. In order to
do, you will have to manually remove the files there associated with
the feature from the eclipse/features directory and its plug-ins from
the eclipse/plugins directory. Be very cautious as to which files you
delete, and always have a backup of your Eclipse directory. If you
remove the wrong files from these directories, you may have quite some
trouble restoring your Eclipse to a stable state. Therefore, unless
your hard disk storage capacity is extraordinarily limited, it is
recommended that you simply leave the physical files in place.
Note that when manually removing plugins as described above, it is
likely that some metadata will still cached by Eclipse. This can lead
to problems later on. Running Eclipse with the -clean option may help
with that, as it causes Eclipse to clean the cached metadata. See the
Running Eclipse help page for details about this option.
Source: http://wiki.eclipse.org/FAQ_How_do_I_remove_a_plug-in%3F
You cannot do this ideally, because the plugins designed for eclipse leave their temp access files even if they are uninstalled, to do so, you will have to follow the steps:
Uninstall the Plugin: You can use the Eclipse UI directly. Go to Help > About Eclipse > Installation Details, select the software you no longer want and click Uninstall.
Delete the Present temp Files in the System, make sure to re-check the dependencies(Note: Removing Dependent Plugins might cause Eclipse to stop Working).
Remove the plugins from the workspace, or in short you can re-configure a new workspace.
This would be removing the plugins, but removing its traces manually.
ref#Link
A ways back I had tried to install the M2E plugin to experiment with Maven. The installation did not go as planned and it left me feeling like I only "half-installed" it. My reasons for this were numerous, but for instance Maven features that should have been present upon restart were simply not there.
I am now trying to download a plugin called EclEmma which is a code coverage analysis tool. The official website has the installation instructions very well spelled out, and I have followed these instructions verbatim.
In the Help >> Install New Software window, I am able to visit the EclEmma update site and select the plugin I want to install. I then click the Next button, whereby I get the following error:
The operation cannot be completed.
Cannot complete the install because one or more required
items could not be found.
Software currently installed: Shared profile 1.0.0.1320083707332
(SharedProfile_SDKProfile 1.0.0.1320083707332)
Missing requirement: Shared profile 1.0.0.1320083707332
(SharedProfile_SDKProfile 1.0.0.1320083707332) requires 'org.maven.ide.eclipse
[1.0.100.20110804-1717]' but it could not be found
According to EclEmma's site, there are no dependencies or prerequisites for this download, and certainly nothing from Maven.
I think I must have mis-installed M2E all those months ago, and somehow it is causing EclEmma to tweak out during installation.
I have now spent an hour trying to figure out how to un-install M2E, but: (a) when I go to the list of installed plugins, the "Uninstall" button remains disabled and I am unable to get it to become enabled, and (b) most of the documentation I've found online seems to suggest that uninstalling plugins is discouraged and possibly even impossible!
How do uninstall M2E? Or at least disable/deactivate all its features so that I can get EclEmma to install? Of course, I could be misinterpreting the error message above...
Thanks for any help!
You might be able to revert Eclipse to a previous configuration of plugins/features, see Reverting to a previous install configuration
I downloaded the sample Restlet project and opened it in Eclipse. I instantly get this error:
Errors occurred during the build.
Errors running builder 'Google WebApp Project Validator' on project 'org.restlet.example.serialization.gae-gwt'.
java.lang.NullPointerException
What am I doing wrong?
I had this same error with my own project. In the Eclipse Project Explorer I right-clicked the project and chose Refresh. That cleared up the error for me.
This is a temporary, but repeatable solution someone on my team found...
Close project
Close Eclipse
Open Eclipse
Open project
I continually had this problem in combination with git. My git repository was in my eclipse workspace ( even though eclipse warns you not to do this ). Deleting the old repository, and creating a new git repository outside of the eclipse workspace, then cloning a fresh copy of my gwt project solved this problem for me. Hope this helps.
I'm also experiencing this error, but thanks to git comparing .classpath I noticed that I had removed a couple of variables from the "Configure Variables" list, but not from the Java Build Path. Once I removed it from the second list, the error was gone.
I got this error when I was using a workspace that was on an NFS and I had the same workspace open on two different vnc sessions. I closed out Eclipse on one vnc session and then restarted eclipse on the other. Then I went to the java build path and editted the gwt sdk and had it use the gwt sdk it was already pointed to and it stopped giving me that error. I didn't actually change the gwt sdk, just went through the motions of doing so. Hope this helps.
The problem was miss configuration of JRE, I just did the following:
Go to Build path configuration, select add Library, JRE System Library, select your JRE.
And there you go...
For me this error seemed to occur after a compile had failed due to lack of memory and eclipse had been restarted. However, after increasing memory (in the eclipse.ini) the problem still persisted. None of the above solutions worked for me.
The bizarre solution I found: our project here uses GWT 2.4, so I switched to 2.5 (which comes with the plugin - window>preferences>google>Web Tookit), re-compiled, switched back to 2.4 and, hey presto, it worked again!
(Another hour of my life I'll never get back!)