I think P2 is much more complicated (and has a lot more possibilities)
than the classic update manager and like you said: hard to find
documentation.
I had a closer look to the wiki-pages of P2 and I noticed that the classic
update manager is still present in Eclipse 3.4 (for backwards
compatibility) but by default P2 is used. So the code - found at
http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/msg05356.html -
i use to update my application at startup will still work in Eclipse 3.4.
is the classic update manager going to disappear in one of the following
releases of eclipse? why should someone use the new p2-system if the only
thing he needs is an automatic update at startup?
if you want to adopt p2 and you have an update site the only thing you
have to do nothing, unless you want to eliminate the slowness, then you
have to launch the metadata generator. and then you can use the new p2
update functionality. but what are the steps to p2-enable your application
with plugins and/or features? i tried the tutorial made by Kai T.
(http://toedter.com/blog/?p=27) but when i'm supposed to use the director
app to install the app, i get some error. so if i can't p2-enable a simple
demo-app, it's no use to start trying it with our application (i use
Eclipse SDK, Version: 3.4.1, Build id: M20080911-1700)