JEP 162: Prepare for Modularization (original) (raw)

Owner Alan Bateman
Type Feature
Scope SE
Status Closed / Delivered
Release 8
JSRs 173 MR, 206 MR, 337
Discussion jigsaw dash dev at openjdk dot java dot net
Effort M
Duration M
Blocks JEP 179: Document JDK API Support and Stability
Relates to JEP 220: Modular Run-Time Images
Endorsed by Mark Reinhold
Created 2012/08/31 20:00
Updated 2017/06/14 20:12
Issue 8046152

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:

java.util.logging.LogManager.addPropertyChangeListener  
java.util.logging.LogManager.removePropertyChangeListener  
java.util.jar.Pack200.Packer.addPropertyChangeListener  
java.util.jar.Pack200.Packer.removePropertyChangeListener  
java.util.jar.Pack200.Unpacker.addPropertyChangeListener  
java.util.jar.Pack200.Unpacker.removePropertyChangeListener  

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