-
Enhancement
-
Resolution: Fixed
-
P2
-
None
-
b163
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8178168 | 10 | Alan Bateman | P2 | Resolved | Fixed | b04 |
- ModuleTarget moves from a standard to a JDK-specific class file attribute. This involves small updates to the ModuleDescriptor and Builder APIs, small updates to jlink, and dropping the `jmod --os-version` option.
- ModuleDescriptor::versionString and ModuleDescriptor.Requires.compiledVersionString to align with the proposal in JSR 376 to allow for alternative module systems that want to use version strings that can't be parsed as a ModuleDescriptor.Version.
- Update Layer API to specify how qualified exports/opens are reified when creating a layer.
- Improvements to resource encapsulation to allow the ClassLoader APIs locate directories in module artifacts or exploded modules as resources. This improves the compatibility for code relying on unspecified behavior when it moves from the class path to the module path.
- Lookup.defineClass as a supported way to defineClasses without needing to break into ClassLoader.defineClass.
- New `java --permit-illegal-access` option that opens all packages for access that would otherwise fail with IllegalAccessException and InaccessibleObjectException. This option is for migration purposes and makes it easier to identify code that relies on breaking into the JDK modules or is using core reflection anti-patterns. Warnings are printed to stderr then access succeeds because of this command line option (or the existing --add-exports/--add-opens options).
- Small implementation changes to the module system initialization so that a confusing stack trace is not printed when module system initialization fails.
- backported by
-
JDK-8178168 Module system implementation refresh (3/2017)
- Resolved
- csr of
-
CCC-8174823 Module system implementation refresh (3/2017)
- Closed
- relates to
-
JDK-8175819 OS name and arch in JMOD files should match the values as in the bundle names
- Closed
-
JDK-8174825 Layer::defineModulesXXX + qualified exports/opens not specified
- Resolved
-
JDK-8175017 Do not print stack trace if initPhase2 fails
- Resolved
-
JDK-8175958 Duplicate module names allowed in exports_to_index, opens_to_index tables
- Resolved
-
JDK-8177139 ServiceLoader no longer detects duplicates on the class path
- Resolved
-
JDK-8177140 Resources in automatic modules should not be encapsulated
- Resolved
-
JDK-8176475 Xcheck:jni warnings in Module code - WARNING: JNI local refs: N, exceeds capacity: M
- Resolved
-
JDK-8177474 Do not emit warnings when illegal access is allowed by --add-exports/--add-opens
- Closed
-
JDK-8179200 "Request authentication" dialog from Java is blank
- Closed
-
JDK-8173946 Resource names used by the ClassLoader/Class/ModuleReader APIs should be specified clearly
- Resolved
-
JDK-8177086 java.lang.reflect.AccessibleObject::canAccess should share access cache with internal method ::checkAccess
- Resolved
- links to