JEP 398: Deprecate the Applet API for Removal

OwnerAndy Herrick
TypeFeature
ScopeSE
StatusCompleted
Release17
Componentclient-libs / java.awt
Discussionawt dash dev at openjdk dot java dot net
EffortS
DurationS
Relates toJEP 289: Deprecate the Applet API
Reviewed byAlexander Matveev, Kevin Rushforth, Philip Race, Sergey Bylokhov
Endorsed byKevin Rushforth
Created2020/11/10 15:54
Updated2021/04/09 20:06
Issue8256145

Summary

Deprecate the Applet API for removal. It is essentially irrelevant since all web-browser vendors have either removed support for Java browser plug-ins or announced plans to do so.

History

The Applet API was previously deprecated, though not for removal, by JEP 289 in Java 9.

Description

Deprecate, for removal, these classes and interfaces of the standard Java API:

Deprecate, for removal, any API elements that reference the above classes and interfaces, including methods and fields in:

Testing

Hundreds of tests need to be either modified or removed before the Applet API is removed, but this JEP is solely about deprecation-for-removal. We will review these tests to determine if further @SuppressWarnings annotations are required.

Risks and Assumptions

In case remaining uses of these APIs do exist, developers can suppress compiler warnings via the @SuppressWarnings("removal") annotation or the -Xlint:-removal command-line option of the javac compiler.