Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Problem compiling with 9 for 8 Date: Mon, 2 Oct 2017 20:24:23 -0400 Organization: Aioe.org NNTP Server Lines: 26 Message-ID: References: NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:37526 On 10/2/2017 8:12 PM, Arne Vajhøj wrote: > But I was wrong about the implementation. > > It does not use the old rt.jar. > > https://bugs.openjdk.java.net/browse/JDK-8058150 > > > For JDK N and --release M, M < N, signature data of the documented APIs > of release M of the platform is needed. This data is stored in the > $JDK_ROOT/lib/ct.sym file, which is similar, but not the same, as the > file of the same name in JDK 8. The ct.sym file is a ZIP file containing > stripped-down class files corresponding to class files from the target > platform versions. > > > So --release should work without the old rt.jar, but zipinfo on > ct.sym reveals that JavaFX is not included in it. > > So therefore an actual old jfxrt.jar is needed. Some googling reveals that ct.sym was introduced as far back as Java 6. Arne