It's not too late for access control

Robert Muir rcmuir at gmail.com
Thu Jul 14 11:37:06 UTC 2016


On Tue, Jul 12, 2016 at 4:25 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:

> Going off-topic slightly but when you do run into issues and if they aren't
> already listed as compatibility issues then please bring them up. So far
> then I think the vast majority of issues that we have heard about relate to
> the changes in JEP 220 (tools.jar going away etc), JEP 223 and the new
> version-string scheme, the class file version bump in jdk-9+119, and then
> all the issues that we have listed in JEP 261. Any help getting bugs
> submitted to projects would be appreciated too.
>

Java 9 breaks log4j 1.2.x out of box. Think about how widely used that
one is! And its no longer maintained!

Sure, its only if you use MDC, and its not even Jigsaw that does it
(relates to version changes). See
https://github.com/elastic/elasticsearch/blob/f01f15d3b8592db4210f725f0c37baff4a554a35/core/src/main/java/org/apache/log4j/Java9Hack.java
if you want a hack.

Its just an example of how much software won't work with java 9 out of
box. Still looking forward to it!


More information about the jigsaw-dev mailing list