You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2019/11/21 15:09:00 UTC

[jira] [Created] (FLINK-14905) Unify packaging process

Chesnay Schepler created FLINK-14905:
----------------------------------------

             Summary: Unify packaging process
                 Key: FLINK-14905
                 URL: https://issues.apache.org/jira/browse/FLINK-14905
             Project: Flink
          Issue Type: Sub-task
          Components: Build System
            Reporter: Chesnay Schepler
            Assignee: Chesnay Schepler
             Fix For: 1.10.0


Right now we have a Java 11 profile for customizing the build in various ways, from bumping plugins, setting compiler flags, disabling tests and even some dependencies.

The dependencies bit a problematic since it implies that not all jars created by the Java 8 build process can actually run on Java 11.
This creates an unnecessary burden for users who want to use Java 11 (reminder: the only supported LTS version) as they'd have to compile Flink themselves for Java 11.

Releasing a second set of jars/binaries is out of the question due to the confusion and overhead this would cause, so instead we should ensure that the Java 8 jars are usable on Java 11.

My proposal is to use a multi-release jar to package additional dependencies that are only loaded on Java 11.
I have verified that this approach works conceptually, whether it works with the dependency we have to deal with (jaxb-api) remains to be seen.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)