On Sunday, February 16, 2020 at 7:58:03 AM UTC-7, Mark Waite wrote: > > > On Sun, Feb 16, 2020 at 7:29 AM Jesse Glick wrote: > >> Could you file this in JIRA please with the smallest steps to reproduce >> you have? >> >> > Yes, I've copied those steps into a Jira ticket > <https://issues.jenkins-ci.org/browse/JENKINS-61105>. I'm not aware of > any of the steps that can be removed, so I believe those are the minimum > steps to duplicate the issue. > > >> Does this occur in `master`? >> > > I don't know if it occurs with 'master'. It does not occur with 2.204.2. > It does not occur with weekly 2.220 as downloaded from the official release > site. I'll build the master branch and try it later today. > > I'll also try to confirm my suspicion that the root of the issue is that > the release candidate build was compiled with Java 11 without specifically > mandating '-release 8' The links included in the earlier message seem to > indicate that setting source and target are necessary but not sufficient > for Java 11 to generate Java 8 byte code. > > I've compared the manifest from Jenkins 2.204.2 with the manifest from Jenkins 2.204.3 rc. The key difference appears to be:
Jenkins 2.204.2: Build-Jdk-Spec: 1.8 Jenkins 2.204.3 rc: Build-Jdk-Spec: 11 I think we need a rebuild of the 2.204.3 release candidate using JDK 8. Mark Waite > I've switched my testing of the release candidate to use Java 11 and that > testing has found no issues. The problem does not occur when the same > release candidate bits are run with Java 11. It only happens with Java 8. > > Mark Waite > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/736b81e6-10cf-4762-95cb-4cfe4aacecfd%40googlegroups.com.
