https://bugzilla.redhat.com/show_bug.cgi?id=1302131
--- Comment #2 from Mat Booth <mat.booth(a)redhat.com> ---
(In reply to Roland Grunberg from comment #1)
Regarding CDT Arduino bringing in PDE, and JDT (which you're
right, is
crazy) :
It looks like org.eclipse.cdt.arduino.ui -> org.eclipse.remote.ui ->
org.eclipse.ui.trace , and org.eclipse.ui.trace is something packaged as
part of the Eclipse PDE UI, which then brings in the JDT. The requirement
for org.eclipse.ui.trace is only so that the
org.eclipse.ui.trace.traceComponents extension point may be used
(
http://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.pde.doc.
user%2Freference%2Fextension-points%2Forg_eclipse_ui_trace_traceComponents.
html) . I think making the dependency optional could resolve this and I
would even argue that it's an upstream bug.
On the other hand this can also be considered a Fedora packaging bug.
org.eclipse.ui.trace ships upstream in the SDK but not in the platform
product so there's some justification for placing it in PDE. However it has
no dependency on other PDE components, so maybe placing it in platform would
make more sense from a user download -size perspective.
Mat, thoughts ?
You're probably right that this dep should be optional.
I was looking for what the idiomatic usage of this extension point is and
interestingly, if you look at org.eclipse.jdt.debug or
org.eclipse.jdt.launching which also make use of it, you'll find no deps on
org.eclipse.ui.trace in their manifests.
--
You are receiving this mail because:
You are on the CC list for the bug.