Re: [platform-update-dev] eclipse installation site types cleanup

[Dorian Birsan <birsan@xxxxxxxxxx>]

Based on all the good feedback so far,
my understanding is this:

1. It looks like everybody is OK with
rolling the private install location into the product extension location.

2. For backwards compatibility reasons,
and all the reasons that were there in the first place, the product extension
will have the following layout:

  <eclipse_product_extension_site>\
                    
                     
        eclipse\ 
                    
                     
                   .eclipseextension
                    
                     
                   features\
                    
                     
                   plugins\


The links directory and the "Add
product extension" file dialog will have to select a path to <eclipse_product_extension_site>
and do the appropriate validation.


3. I think we're not too clear on the
supported or desired semantics of the stand-alone update commands.
(BTW, a brief description of the commands
is documented here: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/doc/working/documentation/standalone_update.html.
)

The requirement for the stand-alone
commands was to allow running update operations from the command line without
having to open the eclipse update manager UI. That's why I disagree a bit
with Peter's notion that users should not be able to undo the result of
a stand-alone command (such as addSite) using the UI.
I do agree that the update manager configuration
dialog is an advanced feature and should not be regularly used by end-users,
unless they know what they're doing or have been instructed by a product
support team. 
As Peter suggests, using activities
to enable/disable the "Manage Configuration" actions is interesting.
See this bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=52820) for
how this can be accomplished.
So, I think the stand-alone commands
addSite and removeSite(this one is not yet implemented) should be the equivalent
of the UI actions to add a site and to remove a site (this one is not yet
implemented).
Peter, still feeling strongly about
added site via command not removable via the UI? If the links are not deprecated,
would you even have a need for this command?


Jan, please take a look at the above
url for stand-alone commands and let me know if it addresses your update
concerns. 

-Dorian