Brian de Alwis

I'm not sure how to handle referencing the Eclipse Docker Tools (which includes the Docker Editor) as they have separate versions for Oxygen and Photon. We may be lucky and...

(4) might be the right answer. The Eclipse Docker Tools marketplace entry has a special `fileExtension_Dockerfile` tag which is used by Eclipse to lookup editors from the Eclipse Marketplace for...

This is the same as #1977 right?

We could suggest looking at the deployment console as an interim measure.

We're using the client libraries, but we have a [test that the `Storage` API returns a `www.googleapis.com` element](https://github.com/GoogleCloudPlatform/google-cloud-eclipse/blob/master/plugins/com.google.cloud.tools.eclipse.googleapis.test/src/com/google/cloud/tools/eclipse/googleapis/internal/GoogleApiFactoryTest.java#L87).

Should this be raised elsewhere? Some errors, like an invalid runtime (e.g., `FOO`) are properly prefixed and picked up.

Ah, XML validation errors are logged differently. But it should be impossible to deploy in such situations as our deploy handler refuses to run if there are any problems markers...

Oops, good point!

The Eclipse [_Update_ checker](http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.updatechecker/src/org/eclipse/equinox/internal/p2/updatechecker/UpdateChecker.java?h=master) is p2-specific and unfortunately there's not much that can be leveraged for our needs. We could load the preferences settings (see [`ProgressConstants`](http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.ui.sdk.scheduler/src/org/eclipse/equinox/internal/p2/ui/sdk/scheduler/PreferenceConstants.java?h=master#n20) and [`AutomaticUpdateScheduler#scheduleUpdate()`](http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.ui.sdk.scheduler/src/org/eclipse/equinox/internal/p2/ui/sdk/scheduler/AutomaticUpdateScheduler.java?h=master#n124)), though unfortunately...

Re-opening as we only _install_ on deploy and local run: we don't perform updates. We could easily do this on startup.