Re: [platform-update-dev] Update Manager Installs - Forcing the Use of a

[Pat McCarthy <patmc@xxxxxxxxxx>]

Glad to get your view Peter - I was
going to ping you if you didn't chime in.... :-)

I don't disagree with your view at all
- I agree completely for the scope I have in mind.  In fact - My goal
would be to have a trigger that would make the use of an Update Manager
only install approach valid only when the install consists of just feature/plugin
content.  This "rule" could be one used by any tool/product
platform that wants to attract a coordinated/supported set of extension
technology - it is not an Eclipse rule.

There may be room for limited use of
an install handler if the scope of processing is something like "automating
the definition of settings and variables in the Eclipse platform",
but not if it is being used to add additional layers of non-plugin software
to the environment.  Once the trigger point has occurred - only a
standard software install would be valid.  That said, there are probably
plugin activation checks that could be used to perform the same setup processing
as part of on-time logic included in the plug-in's startup method.

This discussion is leading to a place
that is not related to what the Eclipse platform's Update Manager technology
can/can't do...  As in the past - we have not always supported all
of the Update Manager capabilities in tool/product specific scenarios.
I'm just trying to see if we can find a way to add support for some of
what Update Manager can do now that we have a single configuration per
install.

Pat McCarthy