RFR: JDK-8186087: jar tool fails to create a multi-release jar when validating nested classes

Xueming Shen xueming.shen at oracle.com
Tue Nov 28 02:57:15 UTC 2017


Please help review the change for #8186087

Issue: https://bugs.openjdk.java.net/browse/JDK-8186087
webrev: http://cr.openjdk.java.net/~sherman/8186087/webrev

The proposed change is to handle the "outer class" of a  nested class 
correctly, instead of simply
relying on "top level" class. Other than that, a "minor" change is to 
also stop trying to "validate"
the non-class/resource entries, for example, if you have a resource 
"foo" both in the base and
versioned directory, and with different "content", currently 
implementation throws a warning
message, which does not appear to be desired and appropriate.

There is a "known/open" issue during discussion regarding how to handle 
the entry that its class
name does not match its entry name (for example, class p.foo.class is 
located at bar/p/foo.class,
currently jar.validator fails the validation with error msg). It appears 
to be a separate issue, so
I'm leaving that one of this one for now.


More information about the core-libs-dev mailing list