[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [platform-ui-dev] [eclipse-pmc] Request PMC approval for removal of (transitively) public method in InlineAnnotationSupprot
- From: "Mike Wilson" <Mike_Wilson@xxxxxxxxxx>
- Date: Mon, 19 Mar 2018 09:08:56 -0500
- Delivered-to: firstname.lastname@example.org
If leaking this as API really was a mistake, and our confidence is high that there isn't "any use case for which anyone would want to use it", please proceed. +1.
If by some chance someone did need this, is there a valid API based way to get the information?
Mickael Istria ---2018/03/19 05:59:57---Dear PMC, With https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug
From: Mickael Istria <mistria@xxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx, "Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>, Angelo zerr <angelo.zerr@xxxxxxxxx>
Date: 2018/03/19 05:59
Subject: [eclipse-pmc] Request PMC approval for removal of (transitively) public method in InlineAnnotationSupprot
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
With https://bugs.eclipse.org/bugs/show_bug.cgi?id=532130 , we'd like to simplify and improve how iniline annotations/code minings are drawn by moving away from LineSpacingProvider.
I did merge the related patch doing so http://git.eclipse.org/c/platform/eclipse.platform.text.git/commit/?id=2d294da598154bcd7ebf63fa4dc6ae8783304be5 , but then API Tools reported that this was introducing an API breakage: http://download.eclipse.org/eclipse/downloads/drops4/I20180318-2000/apitools/freeze_report.html . API Tools is obviously right here and Dani noticed it promptly and already reverted the patch.
The initial issue comes from earlier implementation that exposed the getLineSpacing method as an inherited public member instead of using composition to hiding it. This method was introduced in M5. Although it wasn't annotated as @noreference and public, this method was never meant to be part of the API and we are not aware of anyone who's referencing it from InlineAnnotationSupport nor of any use case for which anyone would want to use it. So we feel confident that it's a safe thing to get rid of it now.
PMC, please evaluate whether changing this API is acceptable at this point and mention ASAP if and when we can re-apply the suggested patch.
Thanks in advance
Eclipse IDE developer, at Red Hat Developers community
Elected Committer Representative at the Eclipse Foundation board of directors_______________________________________________
eclipse-pmc mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit