Comments on: Reverting Changes in an Eclipse Installation using p2

By: snowplow

snowplow — Tue, 26 Jul 2011 07:28:57 +0000

may you give me the source of the p2 reverting ?

By: Steve Robenalt

Steve Robenalt — Fri, 02 Oct 2009 18:26:09 +0000

Looks like Nick answered my question before I could ask it. Thanks Nick!

By: Chris Aniszczyk

Chris Aniszczyk — Fri, 02 Oct 2009 16:10:00 +0000

Aaron, Eclipse is a level playing field in terms of plug-ins. It's easy to write a bad plug-in that performs a lot of code during startup of itself and slows down a whole Eclipse install. You can even write a plug-in that calls System.exit(1) on startup! There's many ways to be devious or even lazy when developing plug-ins. A common case is that plug-ins don't cleanup after themselves properly so memory is wasted. So I wouldn't necessarily blame the p2 team who is just delivering the bits and ensuring dependencies are properly satisfied. This is one reason we (EclipseSource) produce products like Yoxos SecureSource to ensure that no bad bundles make it into an Eclipse installation.

By: Aaron Digulla

Aaron Digulla — Fri, 02 Oct 2009 09:11:50 +0000

Amazing … that worked for you? Never did for me.

The p2 guys may argue that some of my plugins are faulty … but that sounds to me that the plugin development process still has some way to go. I mean it shouldn’t be possible to deadlock an Eclipse install just by adding another plugin.

By: Nick Boldt

Nick Boldt — Fri, 02 Oct 2009 03:42:03 +0000

Coincidentally, I was just looking up how to do this programmatically via commandline today using p2.director and the -uninstallIU flag.

http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html

By: Jens Cellai

Jens Cellai — Fri, 02 Oct 2009 03:01:48 +0000

I was not aware of this function to do this. Thanks!