Hard to get CT4E logging

[briandealwis]

We do our logging via java.util.logging, which isn't captured by the Eclipse logs. It would be useful to introduce a logging bridge to (somehow) also log to the Eclipse .metadata/.log file. Such bridging would allow seeing errors from the Eclipse Error Log view, and also simplify submitting error reports.

This bridge should be abled to be disabled with a system property, and should also try to detect situations where the com.google.cloud.tools.** is already being logged to something other than the console log (e.g., already being handled by something else).

[elharo]

Just checking, might this ever end up getting auto-submitted to Eclipse project error catchers or any other automated collection agent?

[briandealwis]

Possilbly. It really depends on what the user has configured. I believe AERI, for example, processes results sent to the StatusManager and does matching based on the bundle IDs. Those same collectors already have access to the projects and information on disk, so we wouldn't be opening up additional access.