Re: [eclipse-pmc] Deprecation of MessageXxx classes

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

> +1
to mark from for removal in 4.17

Not really. As
per the rules:

7.  If there
is no substantial community disagreement (the PMC may decide to cancel
the change if the impact of removal outweighs the benefits) and after the
two year waiting period has gone by, the API is removed and the
porting guide entry is moved from the "Planned API removals"
to the "Removed APIs" section in the documentation. In general,
removing a deprecated API does NOT cause the increase of the major version
segment.

But +1 to mark
for removal. Note that we have the last planned 4.16 build today.

Dani



From:
       Lars
Vogel <lars.vogel@xxxxxxxxxxx>
To:
       eclipse-pmc@xxxxxxxxxxx
Date:
       03.06.2020
15:58
Subject:
       [EXTERNAL]
Re: [eclipse-pmc] Deprecation of MessageXxx classes
Sent
by:        eclipse-pmc-bounces@xxxxxxxxxxx

---

Hi Dirk,

+1 to mark from for removal in 4.17, direct deletion is not possible
due to our API guidelines.

Here is what needs to be done (see
https://wiki.eclipse.org/Eclipse/API_Central/API_Removal_Process)
---------
Annotate all APIs that are to be removed with @noreference, @noextend
and @noimplement where applicable, update deprecation comment and add
an entry in the porting guide. Do the same for the API that depends on
it. The deprecation comment and porting guide entry must explain how
to adapt the client code and also include a link to the bug report to
allow feedback from API adopters.
--------
IIRC you requested this already a longer while ago. Please mark them
this time for deletion so that we can retire them in a few years.

Best regards, Lars

On Wed, Jun 3, 2020 at 3:53 PM Dirk Fauth <dirk.fauth@xxxxxxxxx>
wrote:
>
> Dear PMC,
>
> some years ago I introduced the following three interfaces:
>
> MessageConsumer
> MessageSupplier
> MessageFunction
>
> It was because a dependency to Java 8 was not yet available for the
Eclipse Runtime. The idea was always to replace those interfaces with the
java.util.function interfaces. But with publishing the org.eclipse.e4.core.services.nls
package as API the change was not that easy anymore. And I forgot about
it to be honest.
>
> To clean up I would like to remove those interfaces and replace them
with default interfaces. The related bug is https://bugs.eclipse.org/bugs/show_bug.cgi?id=512665
>
> I therefore request for removal of those interfaces.
>
> Greez,
> Dirk
> _______________________________________________
> eclipse-pmc mailing list
> eclipse-pmc@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc



-- 
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc