beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-3422) The jar files uploaded to maven do not work with Java 9
Date Mon, 08 Jan 2018 23:07:00 GMT


ASF GitHub Bot commented on BEAM-3422:

iemejia opened a new pull request #4365: [BEAM-3422] Update reproducible-build-maven-plugin
to version 0.4
   Follow this checklist to help us incorporate your contribution quickly and easily:
    - [x] Make sure there is a [JIRA issue](
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
    - [x] Each commit in the pull request should have a meaningful subject line and body.
    - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
    - [x] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
    - [x] Run `mvn clean verify` to m ake sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> The jar files uploaded to maven do not work with Java 9
> -------------------------------------------------------
>                 Key: BEAM-3422
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: build-system
>    Affects Versions: 2.2.0
>         Environment: OSX Darwin 17.3.0
>            Reporter: Chris Heisterkamp
>            Assignee: Ismaël Mejía
>             Fix For: 2.3.0
> The apache beam jars uploaded to maven have invalid date modified times in the jar files
and cannot be loaded by JDK 9 because of
 I've submitted a new bug to asking that the fix be back ported
to the next Java 9 release.
> In the meantime, can you repackage the jars with valid modified times? And uploaded fixed
jars to Maven?
> To reproduce you just need to put one of the jars on the classpath for javac.  So far
I've found the following jars on maven central are affected.
> beam-runners-google-cloud-dataflow-java-2.2.0.jar
> beam-sdks-common-runner-api-2.2.0.jar
> beam-sdks-java-core-2.2.0.jar
> beam-sdks-java-extensions-google-cloud-platform-core-2.2.0.jar
> beam-sdks-java-extensions-protobuf-2.2.0.jar
> beam-sdks-java-io-google-cloud-platform-2.2.0.jar
> e.g.
> ```
> > curl -O
> > javac -cp beam-sdks-java-core-2.2.0.jar
> An exception has occurred in the compiler (9.0.1). Please file a bug against the Java
compiler via the Java bug reporting page ( after checking the Bug
Database ( for duplicates. Include your program and the following diagnostic
in your report. Thank you.
> java.time.DateTimeException: Invalid value for MonthOfYear (valid values 1 - 12): 0
> 	at java.base/java.time.temporal.ValueRange.checkValidValue(
> 	at java.base/java.time.temporal.ChronoField.checkValidValue(
> 	at java.base/java.time.LocalDate.of(
> 	at java.base/java.time.LocalDateTime.of(
> 	at jdk.zipfs/jdk.nio.zipfs.ZipUtils.dosToJavaTime(
> 	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem$Entry.cen(
> 	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem$Entry.readCEN(
> 	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.getEntry(
> 	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.newInputStream(
> 	at jdk.zipfs/jdk.nio.zipfs.JarFileSystem.isMultiReleaseJar(
> 	at jdk.zipfs/jdk.nio.zipfs.JarFileSystem.<init>(
> 	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.newFileSystem(
> 	at jdk.compiler/$ArchiveContainer.<init>(
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/$addRootPackageFor$7(
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/$JCCompilationUnit.accept(
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> 	at jdk.compiler/
> > java -version
> java version "9.0.1"
> Java(TM) SE Runtime Environment (build 9.0.1+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
> ```
> Unpacking and re-creating the jar with JDK 8 fixes the problem on OSX
> jar -xf beam-sdks-java-core-2.2.0.jar
> jar -cf beam-sdks-java-core-2.2.0.jar .
> You call also use the test from
to look at the modified dates for the jar entries.

This message was sent by Atlassian JIRA

View raw message