|Re: [cross-project-issues-dev] HTMLPrinter is Broken|
I have read the whole thread.
On 25.01.2018 17:44, Leo Ufimtsev wrote:
It's definitely best avoided, when possible, but that's the caveat. When it's not possible to implement JDT without using UI internals and it's not possible to implement PDE without p2 internals then axiomatically it follows that others wanting to implement cool functionality like these projects do will find themselves in the same boat.
The Eclipse itself runtime does exactly that: https://bugs.eclipse.org/bugs/show_bug.cgi?id=502209
Yes, it's less than ideal, with the added huge disadvantage that you only see failures at runtime, so the tests better be good.
Yet the platform project's own teams make a habit of this practice. That too would appear to be unjustifiable.
I understand that you primarily see this as black or white, but thank goodness the JDT team doesn't take this attitude and sees all the shades of gray between the extremes.
I can only suggest that you look carefully within your glass house, making sure its furnishings set the highest standard with regard to the fundamental principles according to which you expect others to furnish their houses.
Back to the top