I install eclipse on Ubuntu14.04 for hadoop program, and there're always some troubles with the hadoop plugin. So I install and uninstall eclipse for two times. But I'm not sure whether it was completely removed.
The last time I install eclipse from the Ubuntu software center. I click the uninstall button in the software center and then delete the folder /usr/lib/eclipse(where eclipse installed). But I also find 'eclipse.ini' in /etc. Can I delete the file?
In order to completely remove eclipse, what can I do further?
Yes you can delete the /etc/eclipse.ini file without causing any issues in your system.
Additionally, Eclipse stores personal files (workspace configuration, plugin info etc.) under .eclipse folder in your home directory which may not be removed when you are performing the uninstall.
Assuming you are the only user using eclipse on that machine you may issue the following command to completely remove all personal config files.
rm -rf ~/.eclipse
Related
I have downloaded Eclipse Neon from their official site and then I just ran an installer contained in the compressed folder(I didn't change any of the default installation settings). It is working just fine, but the icon in the sidebar is not displayed correctly when I am running it and the quick search from the sidebar also doesn't find eclipse when searched for. That is why I want to reinstall it, but i don't even know how to remove it completely. I tried Synaptic Packet Manager, but it doesn't work. What should I do?
I'm using Ubuntu 16.04.
Eclipse doesn't have a traditional install or uninstall process. Only a folder of an application is created plus the workspace which you created. If you used the Eclipse Installer, you may also have a bundle pool folder named .p2 under your user home directory. There can also be .eclipse in your user home. Other than that, there shouldn't be anything Eclipse-related. Uninstalling is just removing those folders.
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.
I am using Install4j 6.1.1 to create a new installer that must be smart enough to support 3 installation scenarios:
Create a new installation
Upgrade an existing installation
Upgrade an existing installation that was created using an InstallAnywhere installer
Scenarios 1 and 2 function correctly. With scenario 3 there is a problem with installing a new jre.
If my installer finds an old non-Install4j instance, it invokes the previous version's uninstaller before proceeding with a new install. This seems to work just fine. However, the new bundled JRE is not being installed properly. The Install Files action copies the JRE to the install folder, and then the deletes the bin folder. This results in a corrupted installation that will not execute. I can see this happen- if I open the JRE subfolder during install I can see the jre's lib and bin folders get created and then watch the bin folder get deleted. The jre\lib folder remains. There does not seem to be anything in the installation log to explain what's happening.
Any idea what would cause a bundled JRE to partially install?
I am uninstalling a plugin named X from eclipse uninstall option.
Now to make a clear approach I went to the eclipse plugins directory and delete the plugin jar file from there.
Now I am trying to reinstall the same plug-in and eclipse prompts an error saying
An error occurred during the
org.eclipse.equinox.internal.p2.engine.phases.CheckTrust
phase. session context
was:(profile=epp.package.jee,
phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust,
operand=, action=). Error reading
signed content. The file
"D:\Testing\eclipse-jee-helios-SR1-win32\eclipse\plugins\x_1.1.3.jar"
does not exist
Now how to resolve the above issue
I have similar issue. I deleted those plugins related files from eclipse/plugins and eclipse/features directory. The reason why I did that is because I have already uninstalled the plugins from eclipse but the files remain in both directories.
I solved it by editing the eclipse/artifact.xml. I search all the artifacts with the id of my plugins and remove them. And I am able to reinstall the plugins again :)
You should never delete plugins you installed using the Eclipse installer under Help>Install New Software. Now there is directory used to drop in plugins as jars, which I am assuming you used, if so deleting it would result in the desired behavior assuming you shut down eclipse before hand. If not then you need clean your configuration area. In the future when removing go to Help>Install New Software>Already Installed software, there should be a remove once your there. :)
Goodluck.
As per eclipse documentation
You should not remove plug-ins from Eclipse. Plug-ins should be
installed as features using the Update Manager. The same Update
Manager can be used to disable plug-ins by disabling the feature they
belong to. Run Help > About Eclipse > Installation Details, select the
software you no longer want and click Uninstall. (On Macintosh it is
Eclipse > About Eclipse > Installation Details.) In older versions,
you might need to Run Help > Software Updates > Manage
Configuration..., select the feature of interest, and disable it with
the task shown in the right window.
When a feature is disabled, all its plug-ins will be disabled also.
They are still available on disk, and they can be enabled at any time
in the future.
To physically remove the feature and its plug-ins, you will have to
manually remove the feature from the eclipse/features directory and
its plug-ins from the eclipse/plugins directory. We advise extreme
caution here. Remove the wrong ones, and you may have quite some
trouble restoring your Eclipse to a stable state. Unless you care a
lot about hard disk use, we recommend leaving the plug-ins where they
are.
Note that when manually removing plugins as described above, some
metadata is still cached by Eclipse, which can lead to problems later
on. Running Eclipse with the -clean option can help with that, as it
causes Eclipse to clean the cached metadata
Thanks .. I am not sure what action actually fixed the exact problem i had.
I removed the plugin related files from plugins and features folder, removed entries from the artifact.xml file and opened eclipse with -clean option.
Run eclipse
Rename eclipse exe to eclipse.exe.back
Run updates
Updates executed successfully
We have a custom plug-in. That is, the company where I'm working developed it in house.
I would like to install it as an available plug-in in Eclipse Ganymede. How do I do that?
From what I can figure out, the Eclipse software install only supports installation from Eclipse software update sites.
I went to Help -> Install New Software... -> Add -> Local...
to browse to a folder containing the plug-in. Although the dialog lets me add the directory as an update site, it doesn't work. It expects that directory to be a local Eclipse update site (I think). I get the error
No repository found at file:/G:/TOOLS/...
Next I just copied the plug-in into the plug-in directory under my Eclipse installation. That didn't work either. I also tried copying it into the dropins directory. No dice.
Can anyone enlighten me how to install a plug-in that's not on an "update" site?
Thanks in advance....
Usually an Eclipse plug-in packaged as zip file is install by extracting it into the Eclipse installation directory (or the plugins directory depending on how it is packaged, as it can also extract files in features directory).
Next restart Eclipse with the --clean option.
Did you check the Eclipse error log? Maybe the bundle is failing to deploy for some reason.
Otherwise, create a Feature and Update Site for your plugin as described here. An update site can either be a remote http server (SVN even), or a local directory. The nice thing is that you'll get versioning and the ability to upgrade and uninstall from inside Eclipse. It also makes things easier once your plugin grows into several plugins because they can be bundled together into a single, versioned feature.