RFR(S): 8075253: Multiversion JAR feature: CDS does not support MV-JARs
Paul Sandoz
paul.sandoz at oracle.com
Tue Mar 22 13:19:58 UTC 2016
> On 19 Mar 2016, at 19:02, Steve Drach <steve.drach at oracle.com> wrote:
>
> Yes, it’s a bug.
Not quite sure why that is failing within JarFile given the Attributes.MULTI_RELEASE Name instance is used as the key
isMultiRelease = result = (man != null)
&& man.getMainAttributes().containsKey(MULTI_RELEASE)
? Boolean.TRUE : Boolean.FALSE;
Or even the following should work:
new Attributes.Name("Multi-Release”)
since the Attributes.Name.equals/hashCode operate with case insensitivity.
What am i missing?
> I’m currently working on another bug that requires me to change manifest processing. It will be case insensitive.
>
But it has to be consistent with look up using Attributes.MULTI_RELEASE or new Attributes.Name("Multi-Release”).
Also, the value of the “Multi-Release” attribute is not important, it’s the presence of that attribute name in the manifest that signals whether the JAR is a MR-JAR or not, the value is ignored.
Paul.
More information about the hotspot-runtime-dev
mailing list