openjdk team mailing list archive

[Launchpad Bug Tracker <1800792@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package openjdk-8 - 8u191-b12-0ubuntu0.18.10.1

---------------
openjdk-8 (8u191-b12-0ubuntu0.18.10.1) cosmic-security; urgency=medium

  * Update to 8u191-b12. (Closes: #911925, LP: #1800792)
  * debian/excludelist.jdk.jtx: no longer needed, using ProblemsList.txt
    from upstream now.
  * debian/excludelist.langtools.jtx: upstream testing does not use any
    exclusion list.
  * debian/patches/sec-webrev-8u191-b12*: removed, applied upstream.
  * debian/patches/jdk-8132985-backport-double-free.patch,
    debian/patches/jdk-8139803-backport-warning.patch: fix crash in
    freetypescaler due to double free, thanks to Heikki Aitakangas for
    the report and patches. (Closes: #911847)
  * debian/rules:
    - tar and save JTreport directory.
    - run the same limited set of tests as upstream does.
    - call the same testsuites scripts used for autopkgtest.
    - reenable jdk testsuite.
    - simplified and moved xvfb logic into check-jdk rule.
    - removed jtreg and xvfb build dependency logic and moved the bdeps
      into debian/control.in.
    - added rules to generate autopkgtest scripts from templates.
  * updated dep8 tests:
    - debian/test/control: run hotspot, langtools, and jdk testsuites.
    - debian/tests/hotspot, debian/tests/jdk, debian/tests/langtools:
      add scripts for each testsuite to be run.
    - debian/tests/jtreg-autopkgtest.sh: template to generate the jtreg
      script used by the autopkgtest tests.
    - debian/tests/jtdiff-autopkgtest.sh: used by the scripts to report
      any differences between the autopkgtest and the tests results
      generated during the openjdk package build.
    - debian/tests/jtreg-autopkgtest.sh: used by the scripts to run jtreg
      and put the resulting artifacts in the right places.
    - debian/tests/valid-tests: removed, no longer needed.

 -- Tiago Stürmer Daitx <tiago.daitx@xxxxxxxxxx>  Mon, 19 Nov 2018
11:02:46 +0000

** Changed in: openjdk-8 (Ubuntu Cosmic)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-8 in Ubuntu.
https://bugs.launchpad.net/bugs/1800792

Title:
  Update to openjdk-8 8u181-b13-1ubuntu0.18.04.1 and openjdk-lts
  10.0.2+13-1ubuntu0.18.04.3 breaks Maven builds

Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in openjdk-lts package in Ubuntu:
  Invalid
Status in openjdk-8 source package in Xenial:
  Fix Released
Status in openjdk-lts source package in Xenial:
  Invalid
Status in openjdk-8 source package in Bionic:
  Fix Released
Status in openjdk-lts source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  Fix Released
Status in openjdk-lts source package in Cosmic:
  Invalid
Status in openjdk-10 package in Debian:
  New
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  Today both the OpenJDK 8 and 11 packages were updated. In the case of
  OpenJDK 8 (openjdk-8 in Xenial, Bionic, Cosmic, and Disco):

  openjdk-8-jdk: 8u181-b13-0ubuntu0.18.04.1 → 8u181-b13-1ubuntu0.18.04.1

  OpenJDK 10 (openjdk-lts in Bionic):

  openjdk-11-jdk: 10.0.2+13-1ubuntu0.18.04.2 →
  10.0.2+13-1ubuntu0.18.04.3

  After this update all my local Maven builds fail with a crashed VM.
  From the console output it looks like one of the prerequisites of
  JaCoCo (Java code coverage tool) is no longer met, but I haven't been
  able to figure out what the root cause is.

  This problem occurs with both OpenJDK 8 and 10.

  Reproduction:

  This is one of our projects: https://github.com/LableOrg/java-nicerxvi

  Clone the project, and call `mvn clean install`. For me it now fails
  to build (output attached).

  When I downgrade to 8u162-b12-1 everything works again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1800792/+subscriptions