Lóránd Somogyi

My frustration about Eclipse P2 from the last time grows…

I just wanted to add documentation for few plug-ins today. As usually those documentations are also plug-ins. P2 here we go…

Found the plug-ins in no time. Install…

And wait, wait, wait… (about 5-20 minutes!) while my eclipse is locked, as P2 is modal. Why? At least let me work while P2 figures out if those plug-ins would fit my installation.

Fortunately I can send the install part, – if everything is fine for P2, – to work in background, but that does not lasts so long usually.

As I learned so many times that things ain’t what they look like, I started to browse the Net (after 3h of cooldown). And I found a lot of pro and contra. There is even a recept how to replace P2 with UM.

Now as I retraced the whole thing one again, I can understand both parties. Developers are probably frustrated, while simple users are happy with it, – or at least will be…

I still do not feel P2 mature enough to replace UM (Update Manager), as there are missing features and obvious bugs.

Missing stuff:

• Resolve dependencies automatically – there are a hell a lot of plug-ins, sometimes I just can’t gather myself what do I need. – You need to know the software you’re installing… – this is no good for simple users…
• Show information about the plug-in and its dependencies. Instead of right click, properties…

I’m still frustrated, and I hope it is just because of the absence of the knowledge.

I still need to pull up my plug-ins for 3.4, so I’ll be learning soon…