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
Related
Eclipse has its own built-in Java compiler. Because my eclipse is old, there are some bugs in the compiler, which blocks my works currently.
At the beginning, I tried use Help>Check for updates. This fails and upgrade does not continue because of some plugin is installed locally and the failure of checking these local directory results in exit of whole upgrade.
No repository found at file:/c:/J9%20Development%20Tools/j9dt-update-site/.
Therefore, is it possible to update only two or three plugins in Eclipse?
To remove the problematic local plugin:
Goto Help > Install New Software
Click on Available Software Sites
Uncheck the problematic item and click either Disable or Remove. Give OK.
Try updating
In recent versions of Eclipse (like Luna), you can selectively update the desired plugin.
Just go to Help > Installation Details
Select the plugin you want to update, and then click the Update... button.
Every question dealing with uninstalling/disabling plugins for Eclipse Juno mentions an Uninstall button but I simply can't find it and Eclipse's help for Juno is sadly no help.
Has this ability been eliminated or omitted or is it in some place different for Juno?
The Uninstall... button is available from the About Eclipse dialog. From that dialog click Installation Details and it's under the Installed Software tab. This typically is only available for features, not plugins. If you can find the appropriate feature that contains the plugins you want to eliminate, that should do the trick for you.
If you are unsure of the feature containing the plugin, you can attempt to go the Installation History tab in the Installation Details window and try to Revert to a previous version of Eclipse that didn't have the plugins.
Finally, you can always manually go into your Eclipse installation folder under the plugins directory and remove them manually. This will sometimes require that you run eclipse -clean from your command line/terminal to truly get rid of the plugin. This is probably the most error prone approach as you could cause problems with features/plugins that may depend on the removed plugins.
I do C++ embedded development for the NetBurner platform. They have plug-ins that customize Eclipse and in addition to a build tool-chain they add a Launch Group under the Run Configuration area. Everything was working fine under Indigo (32 bit) when I decided to install Subclipse (big mistake). As soon as the install finished I could no longer run my existing configurations successfully. When I went into the Run Configurations area I noticed the Launch Group I used to use was missing. Here is what it looked like earlier yesterday:
Here's what it looks like today:
Things I've tried
First I uninstalled the Subclipse plugins using the
Help->About->Installation Details and then selecting them one at a
time, Uninstalling and restarting after each uninstall. No change.
Then I unpacked the original Eclipse Indigo/CDT 32 bit download to a
fresh folder. Copied over the NetBurner plugins from the zip I got
from the manufacturer. No change.
Launched with different Workspaces, no change.
Launched a Galileo version, it uses older plug-ins, and it still
works.
Copied older plug-ins into Indigo, the older NetBurner launcher
shows up (but it doesn't really work with Indigo)
Removed the older plug-ins put in the newer ones, old NetBurner
launcher went away new launcher does not show up.
Tried removing the
{Workspace}.metadata.plugins\org.eclipse.debug.core.launches - no
change.
Interestingly even though launches has many .launch files that should show up under Run Configuration, nothing shows up.
One other strange (possibly relevant) thing is that icon for the NetBurner Perspective went away, now it just has <NetBurner> as the text and a generic perspective icon.
I can still cross-compile and build for the NetBurner (i.e. the build toolchain still works), it's just the ability to use run configurations that seems to be missing.
I'm out of ideas, does anyone know of some global setting that sits outside the workspace and outside the Indigo installation folder that could be causing this?
I'm running on Win 7 64 bit ultimate, I run the 32 bit version of Indigo because the 64 bit doesn't appear to work with the NetBurner plug-ins. I've also disabled the two Mylyn tasks under General->Startup and Shutdown (they seemed to cause many Permgen memory crashes). This is the same setup I had working flawlessly yesterday.
Update
I also noticed that only 3 of the 4plug-ins are showing up in the Installation Details plug-in pane. The nbeclipse.core_2.6.0.jar is in the eclipse plugin directory but not showing as loaded. So I guess I know now the problem is the plug-in isn't loading but I don't know why or how to get it to load, or what subclipse could have changed that would cause this.
I suspect that the Subclipse installation may have caused an update to some other plugin(s) that it depended on (keep in mind the transitive nature plugin dependency resolution; if you're installing plugin A and it requires a certain version of Plugin B that you don't have, Plugin B will be installed or updated to that version). In doing so, maybe the NetBurner plugin can no longer load because its declared dependencies are no longer met (ie, it depended on an earlier version and does not tolerate a later version).
You can use the OSGi Console to help determine why a plugin is not loading. Here are a couple of references that should help:
http://grep.elasticpath.com/community/techblog/blog/2010/05/27/eclipse-plugins-and-the-osgi-console
http://www.vogella.com/articles/OSGi/article.html#osgiconsole
By the way, you can not just copy plugins into an Eclipse installation and expect them to work. For several versions now, Eclipse has not supported that ability. You must use Help > Install New Software or File > Import > Install > From Existing Installation to install plugins. Ask the vendor if they have an update site to install from; like I said above, simply dropping things into Eclipse's plugins folder is not supported any more, it won't work. Other than the vendor providing an update site, the only other option is to use the dropins folder, as described here.
I have updated my ubuntu desktop and the eclipse which i was running on the system got updated automatically. After the update all the options inside the eclipse are the same as they used to be by default.. all my customization has been lost and the perspectives, project templates are no more. Now when i tried to installed the plugins, eclipse returns me that the selected plugins has already been installed..
I want to know is it common with eclipse to show this behavior after each update? How to can i get back my old customization without deleting the installed plugin folder and install them from scratch again..
I didn't met the issue you mentioned before. but I suggest you can check whether your workspace location is changed after your plugin is installed/updated.
Actually, all your eclipse plugins configuration/preferences settings are stored into your {workspace_home}.metadata folder. it's not relevant about what plugin eclipse has installed, That's the reason why each time switch workspace, you need to re-customized preferences settings.
So, if you want to protect customized settings, pls consider backup .metadata folder properly.
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.