Community
Participate
Working Groups
The discovery component checks for a content.jar file to verify if an update site is valid. This breaks update sites that do not provide P2 meta-data but still have a site.xml. Since this is still a common scenario the validation code should also check for a site.xml if the content.jar is not available and as a fall-back check for content.xml in case the meta-data is not compressed. These checks should be cheap if HEAD requests are issued in the same HTTP connection.
from call: verify sites with/without metadata, but don't filter them outright. Present them differently in UI
Site verification has been modified. Also as per call, components are not filtered out if the site is unavailable: some kind of indication in the UI will show the user that the connector is probably unavailable.
Mik how would you like to display connectors where the update site URL was either unavailable or had some other kind of problem? It was suggested that a warning decoration icon be used. That sounds good to me -- but where would the decoration appear. Would we also provide a tooltip on it to indicate what the warning is about?
How about disabling that row (preferrably by setting it's style to SWT.GRAY since that looks prettier) and putting in a warning on the wizard page that says something like "Some connectors sites could not be contacted and appear in gray".
in latest row is now disabled. I couldn't find SWT.GRAY, so instead set the foreground color. I tried the wizard warning, however the result was less than optimal: the wizard page instructions are no longer visible. Instead a warning dialog popup occurs if an attempt is made to select any of the disabled items. Please let me know if you think this is a good idea.
Sounds good.
