| Classic Update Capability and P2 [message #112217] |
Thu, 19 June 2008 16:44 |
 Mark Melvin
Messages: 118
Registered: July 2009 |
Senior Member |
|
|
Hi There,
For various reasons we are not able to ship our product based on P2 - the
main reason being we heavily depend on install handlers and simply do not
have time to port everything to touchpoints. So, for our upcoming release
to be based on Eclipse 3.4 we are planning on continuing to use the old
Update Manager. Up until now for our internal milestone releases based on
Eclipse 3.4, I have been using the script to manually remove P2 from the
version of the Eclipse platform that we install. Because we would like to
*eventually* move to P2 I would like to leave P2 alone and ship on a
standard Eclipse 3.4 platform runtime. So my question is - will this
create "issues" if I do not remove P2 from the platform, but essentially
use the Update Manager exclusively for the time being?
Secondly, our installer will be calling the update manager from the
command line to do its installation/uninstallation of features. Do I need
to specifically "enable" the update manager to avoid problems or am I
correct in assuming that the Update Manager Capability that is turned off
by default is simply a UI filter and does not prevent the update manager
plugins from loading if required? Also, would it cause problems to enable
this capability while P2 is installed?
Can anyone think of any other issues I may encounter?
Thanks in advance,
Mark.
|
|
|
Powered by
FUDForum. Page generated in 0.02711 seconds
] 
Search
Help
Register
Login
Home
