Community
Participate
Working Groups
Follow up from bug 307524. PDE should remove its documentCreation extension for XML documents/PDE editors when WST removes their extension for XML documents. Bug 268635 has been filed against WST for this.
*** Bug 351475 has been marked as a duplicate of this bug. ***
Short of removing ours, which would be a large an API breaking undertaking, which test suites would our document implementation need to pass for the PDE to be comfortable removing theirs?
(In reply to Nitin Dahyabhai from comment #2) > Short of removing ours, which would be a large an API breaking undertaking, > which test suites would our document implementation need to pass for the PDE > to be comfortable removing theirs? I was not involved in the original bug. But I would only consider removing PDE's documentCreation extensions, if WST ensures that the default document is created for all PDE content types. Any test suite - even if complete ATM - would become outdated. Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=307524#c18: > It is known since 3.2 (4 years!) that the extension point must no longer be > used. Those who do so take into account that they break other plug-ins - > like in this case. The only valid use case for using the extension point is > if the client is 100% sure to own that content type / extension, which is > clearly not the case here.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.