Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Simplified API removal process for Java code

Hi Lars and the rest of the Eclipse PMC,

This sounds like a simplification of the process. However it leaves one thing unclear to me. After the API has been removed, will that be documented? Will it be added to at the time of removal? That removal document is linked from the migration guide in each release.


Jonah Graham
Kichwa Coders

On Wed, 17 Aug 2022 at 11:51, Lars Vogel <lars.vogel@xxxxxxxxxxx> wrote:

We simplified the rules to mark deprecated API for deletion.

For Java code you can use "only" the @Deprecation annotation with the
correct flags instead of also adding a manual entry to our API removal
document. This will result in an entry of the Javadoc page.

 * @noextend This class is not intended to be subclassed by clients.
 * @noreference This class is not intended to be referenced by clients.
 * @noinstantiate This class is not intended to be instantiated by clients.
 * @deprecated Use
 *             {@link
 *             instead, which does not use {@code} as that package
 *             is planned to be removed.
@Deprecated(forRemoval = true, since = "4.25")



I moved this also to our guideline wiki, re-using infos from the old wiki

All the rest of the rules are still the same, for example you still
need PMC approval to mark API for removal and we still have to keep
the API for a minimum of two years after marking it for removal.

Best regards, Lars
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:
eclipse-dev mailing list
To unsubscribe from this list, visit

Back to the top