Move org.eclipse.ui.trace -> platform.ui

[laeubi]

PDE currently hosts a plugin named org.eclipse.ui.trace beside its naming it also does not has any dependency to PDE at all. It is also nowhere referenced except from feature org.eclipse.pde

[HannesWell]

I assume it's in PDE because it's developer tooling and somehow similar to the E4-spies.

[laeubi]

I assume it's in PDE because it's developer tooling and somehow similar to the E4-spies.

As far as I understand it offers to configure the trace levels, what would be more equinox than PDE but then still I wonder why its org.eclipse.ui.trace naming... So I think it could be more generally be in platform.ui I don't really see this is useful only for plugin development.

[mickaelistria]

I think @HannesWell is right, this bundle probably made its way into PDE because it's target audience are "Plug-In Developers".
However, enabling trace could be something that developer may request a user to enable (if the code leverages traces), it's more or less an advanced version of logging. So maybe it'd make sense to put this plugin in main repo and main product independently of PDE, so we know most users can enable trace and we can more easily ask for more details.

[iloveeclipse]

Yes, tracing is actually generic enough and useful without PDE for reasons Mickael provided.
If someone want to move it for 4.35, it should be done very soon, before M3 in two weeks from now.

[laeubi]

I think there is no immediate need so we can easily wait for next stream open time, but I thought it would be good to discuss already.