Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 540289

Summary:	manifest attribute "Multi-Release: true" should be checked during ClasspathMultiReleaseJar creation
Product:	[Eclipse Project] JDT	Reporter:	Till Brychcy <register.eclipse>
Component:	Core	Assignee:	Jay Arthanareeswaran <jarthana>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.9
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=540274
Whiteboard:	bulk move

Description Till Brychcy

2018-10-19 02:10:04 EDT

While looking at bug 540274, I noticed that ClasspathMultiReleaseJar creation is always done if compiliance is 9 or higher.

But http://openjdk.java.net/jeps/238 says:

A multi-release JAR ("MRJAR") will contain the main attribute:
Multi-Release: true

Alan Bateman also confirmed this in a recent answer to a question on jigsaw-dev: http://mail.openjdk.java.net/pipermail/jigsaw-dev/2018-October/013952.html

Either ClasspathMultiReleaseJar should  not be created at all if it is missing, or the initializeVersions()-method should look for it and only look for versions if it is present.

Comment 1 Till Brychcy

2018-10-19 02:12:49 EDT

@Jay, as ClasspathMultiReleaseJar is recent code by you, I'm setting you as assignee, I hope thats ok.
I'm also setting the target milestone so this doesn't get overlooked.

Comment 2 Jay Arthanareeswaran

2018-11-20 03:46:56 EST

Okay, ran out of time. Will take this up during RC1.

Comment 3 Jay Arthanareeswaran

2018-11-27 01:52:33 EST

Sorry, ran out of time. Moving out of 4.10

Comment 4 Manoj N Palat

2019-02-11 04:27:58 EST

Bulk move out of 4.11

Comment 5 Jay Arthanareeswaran

2019-05-22 00:01:00 EDT

Sorry, have to move out again.

Comment 6 Manoj N Palat

2019-08-27 02:37:18 EDT

Bulk Move Out of 4.13