Hi, I have tested the Java 10/11 compilation and found the following:
Oozie cannot be compiled if we use Java 10/11 + Linux + Hadoop 2.6.x It's possible to compile using Java 11 + Mac + Hadoop 2.6.x or Java 11 + Linux + Hadoop 2.7.x I have opened a jira about this: https://issues.apache.org/jira/browse/OOZIE-3558 Best, Sala On Mon, Nov 11, 2019 at 8:44 PM Attila Sasvári <[email protected]> wrote: > I failed to build Oozie 5.2.0 rc0 with OpenJDK 10 and OpenJDK 8. > > # Oozie 5.2.0 rc0 with Java 10 : > - downloaded > https://people.apache.org/~asalamon74/oozie-5.2.0-rc0/oozie-5.2.0.tar.gz > - extracted it to oozie-5.2.0 > - based on the public OpenJDK 10 Docker image ( > https://hub.docker.com/_/openjdk), created the following Dockerfile to > make > the Oozie distro: > > FROM openjdk:10 > RUN apt update -y > RUN apt install -y maven > COPY oozie-5.2.0 /usr/src/oozie > WORKDIR /usr/src/oozie > RUN bin/mkdistro.sh -DskipTests > > - docker build -f Dockerfile . failed with > > [ERROR] Failed to execute goal on project oozie-fluent-job-api: Could not > resolve dependencies for project > org.apache.oozie:oozie-fluent-job-api:jar:5.2.0: Could not find artifact > jdk.tools:jdk.tools:jar:1.6 at specified path > /usr/lib/jvm/java-10-openjdk-amd64/../lib/tools.jar -> [Help 1] > > when it tried to build the Fluent Job API. > > - Fluent Job API's jaxb dependency seems to rely on the existence of > tools.jar. However, JEP-220 (https://openjdk.java.net/jeps/220) removed > tools.jar and it affects JDK 9+ environments. > > # Oozie 5.2.0 rc0 with Java 8, using the OpenJDK 8 base Docker image: > - Dockerfile > FROM openjdk:8 > RUN apt update -y > RUN apt install -y maven > COPY oozie-5.2.0 /usr/src/oozie > WORKDIR /usr/src/oozie > RUN bin/mkdistro.sh -DskipTests > > Building Apache Oozie WebApp failed with a different error: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-dependency-plugin:3.0.2:copy (copy-sharelib) > on project oozie-webapp: Unable to find/resolve artifact. > com.google.inject.ProvisionException: Unable to provision, see the > following errors: > [ERROR] > [ERROR] 1) Error injecting: private org.eclipse.aether.spi.log.Logger > org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger > [ERROR] while locating > org.apache.maven.repository.internal.DefaultVersionRangeResolver > > Has anyone else experienced similar build failures? > > Regards, > - Attila > > On Sun, Nov 10, 2019 at 10:59 PM Attila Sasvári <[email protected]> > wrote: > > > > Hi Sala, > > > > Many thanks for driving the release. > > > > Can you please outline main changes and new features of Oozie 5.2? > > > > Best, > > - Attila > > > > On Fri, Nov 8, 2019 at 11:15 AM Andras Salamon > <[email protected]> wrote: > >> > >> Hi, > >> > >> I have created a build for Oozie 5.2.0, candidate 0. > >> > >> Keys to verify the signature of the release artifact are available at > >> > >> https://www.apache.org/dist/oozie/KEYS > >> > >> Please download, test, and try it out: > >> > >> https://people.apache.org/~asalamon74/oozie-5.2.0-rc0/ > >> > >> The release, sha512 signature, gpg signature, and rat report can all > >> be found at the above address. > >> > >> Vote closes on Nov 17th. > >> > >> Thanks, > >> Sala >
