JEP 162: Prepare for Modularization

AuthorAlan Bateman
OrganizationOracle
Created2012/8/31
Updated2013/8/22
TypeFeature
StateFunded
Component--/--
ScopeSE
JSR173 MR, 206 MR, 337
RFE7192274, 8000362, 7190273, 7193339, 7169894, 8003562
Discussionjigsaw dash dev at openjdk dot java dot net
EffortM
DurationM
Endorsed-byMark Reinhold
Funded-byOracle
Release8
TargetM7

Summary

Undertake changes to smooth the eventual transition to modules in a future release, provide new tools to help developers prepare for the modular platform, and deprecate certain APIs that are a significant impediment to modularization.

Non-Goals

It is not a goal of this effort to integrate code for the module system, developed in Project Jigsaw, into JDK 8.

Description

In light of the deferral of Project Jigsaw to a later release, this JEP proposes the following changes:

Testing

Changing existing APIs to use java.util.ServiceLoader will likely require the development of new tests.

New command-line tools or runtime options will require new tests.

If a standard PrincipalComparator API is defined then this will require new conformance and unit tests.

Risks and Assumptions

There is a small risk that changing the implementation, to fix assumptions related to class loading for example, may cause side effects. As with all bugs and features then we assume that extensive testing of JDK 8 will uncover such issues.

Impact