-
Enhancement
-
Resolution: Fixed
-
P2
-
8
-
b19
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8068102 | 8u45 | Mandy Chung | P2 | Resolved | Fixed | b02 |
JDK-8069967 | emb-8u47 | Mandy Chung | P2 | Resolved | Fixed | team |
The extension mechanism [1] allows jar files containing APIs that extend the Java SE Platform to be installed into a run-time image so that their contents are visible to every application that is compiled with or runs on that image.
The extension mechanism was introduced in JDK 1.2, which was released in 1998, but in modern times we have seen little evidence of its use. This is not surprising, since most Java applications today place the libraries that they need directly on the class path rather than require that those libraries be installed as extensions of the run-time system.
This feature will be deprecated in 8u40 and may be removed in a future JDK release [2]. There is no change to the runtime behavior.
[1] http://docs.oracle.com/javase/8/docs/technotes/guides/extensions/index.html
[2] http://openjdk.java.net/jeps/220
The extension mechanism was introduced in JDK 1.2, which was released in 1998, but in modern times we have seen little evidence of its use. This is not surprising, since most Java applications today place the libraries that they need directly on the class path rather than require that those libraries be installed as extensions of the run-time system.
This feature will be deprecated in 8u40 and may be removed in a future JDK release [2]. There is no change to the runtime behavior.
[1] http://docs.oracle.com/javase/8/docs/technotes/guides/extensions/index.html
[2] http://openjdk.java.net/jeps/220
- backported by
-
JDK-8068102 Deprecate the Extension Mechanism
- Resolved
-
JDK-8069967 Deprecate the Extension Mechanism
- Resolved
- relates to
-
JDK-8148969 Reorganize FX SDK layout to match JDK 9 layout
- Resolved
-
JDK-8064667 Add -XX:+CheckEndorsedAndExtDirs flag to JDK 8
- Resolved