| Update Manager vs. Equinox P2 [message #103214] |
Fri, 04 January 2008 00:53 |
Eclipse User |
|
|
|
Originally posted by: tom.seidel.spiritlink.de
Hi,
After reading the Plans for P2 and the replacement of the Update-Manager
in Eclipse 3.4 I have several questions to P2 (I already got some
answers while browsing the code and the wiki).
We're developing RCP Applications where the "old" update-manager
couldn't fulfill our requirements. So we extended these plugins and
provided a web-application that "calculates", based on the clients
configuration and acl, site.xml files which were responded to the
eclipse-client. So there was no need to change the internals of the
update-manager.
Now we're very interested to switch to P2. For us is the "pure
provisioning-aspect" not so important, in general our customers have
only one client with one configuration. More important is the logic that
will be executed on the server. P2 will also generate Metadata (like the
site.xml), but are these files static or will be there a possibility to
"calculate" meta-data files based on customizable aspects? Unfortunately
I couldn't find much information about the functionalities the
metadata-repository provides.
The main point I'm interested in is: What are the new features p2
provides in comparison to the update-manager (expecting the "pure
provisioning-aspect")? Especially what are the functionalities located
on the update-server?
And what are the fundamental changes in the structure of a RCP
Application, e.g. do I have to distribute all my current features as
installable units?
Another point: Is the P2 in a commercial Application already usable?-Is
a switch worthwile or is it still too early?
Thanx in advance
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.03075 seconds
] 
Search
Help
Register
Login
Home
