JDK 9 update
Project Jigsaw was promised long ago as a way to allow programmers to write code that included independent modules. Jigsaw’s goal is to define a standard module system for the Java platform and use it to modularize the platform itself and applications. Jigsaw was designed to be included in Java 8, but lost this, so it is now proposed for Java 9.
In a post on the Openjdk mailing list, Mark Reinhold, chief architect of Oracle’s Java platform group, said that the current build implements all the changes described in this JEP, except that the jrt provider: file system has not yet been implemented and the extension mechanism has not yet been removed.
These packages are intended to allow developers to try Project Jigsaw without having to compile it from sources. The builds are available on the JDK 9 project website.
Changes have also been made in some of the Sgps. Jeps, Java Enhancement Proposals, are being used to allow new features to be discussed and developed without going through a full formal specification (JSR). PEC that are popular and successful will be presented as part of the next full formal specification.
Updated Jeps provide unified JVM registry and more build controls.
Unified JVM Logging (JEP 158) will provide a common logging system for all JVM components. This will change the current way the JVM reports events in its subsystems and add common command line options. This JEP was heavily influenced by what exists in Oracle’s JVM Jrockit, according to the proposal.
The second JEP to be updated, JEP 165, proposes to improve the control of JVM compilers by encapsulating control in a set of options. This would allow different sets of options to be applied depending on the method being compiled and opens the possibility to change sets of options during runtime.
Suggestions were made as Jeps (Java Enhancement Proposals). The Pecs provide a path for new features to be discussed and developed without going through a complete formal specification (JSR). The less formal approach makes it possible to make proposals that overcome a specific problem.
The idea is that if a JEP is popular and successful, it will be presented as part of the next complete formal specification. This approach makes it possible to have incremental Jeps, rather than a large group of changes at the same time. This is the first time Jeps have been used and the list that Oracle has come up with is relatively small.
The proposed JEP for JDK 9 starts with improvements to the process API used to control and manage operating system processes. Java SE offers limited support for native operating system processes, with a basic API for setting up the environment and starting a process. The suggestion is that this should be extended so that developers no longer have to resort to native code.
The improvements to the conflict lock are the next suggestion, aiming to improve the performance of the disputed Java object monitors, as measured by a set of benchmarks and tests. This would result in better performance in situations where multiple segments compete for access to objects.
Another JEP is the provision of a segmented code cache that will divide the cache code into distinct segments, each of which contains compiled code of a specific type, to improve performance and allow future extensions. This would be particularly applicable to large applications.
The development of a lightweight JSON API to consume and generate JSON documents and data streams has also been suggested. This would aim to meet the needs of Java developers using JSON.
A better version of Smart Java Compiler (sjavac) is another proposal, Smart Java Compilation Phase 2. The idea is that sjavac should be improved so that it can be used by default in JDK compilation and that it should be generalized so that it can be used to build large projects beyond JDK.
The final JEP is for modular source code. This is an internal exercise to reorganize the JDK source code into modules, improve the build system to compile modules and impose module limits at build time.
The full list of Jeps can be viewed on the Openjdk website.
PHP with JDK?? You are not confused? PHP has nothing to do with JDK, which means java Development kit. Jdk is for java, nothing linked to php.
– user28595
Can you explain it better? I don’t understand the relationship between one thing and the other...
– igventurelli
I am voting to close this question as out of scope because it has become a mess, in addition to unclear has two completely different answers and none answers what the AP wants (which seems to be a mystery)
– Jéf Bueno
After editing, the question was even more "no foot or head". I agree with the closing.
– user28595