Hi All, The missing list for the 5.2.0 RC0:
This release introduces following major changes and fixes: Improved Java 11 compatibility ( OOZIE-3459 ) Improved S3 support ( OOZIE-3529 ) Escape quotes whitespaces in Sqoop <command> field ( OOZIE-2949 ) Exclusion pattern for sharelib JARs ( OOZIE-1624 ) Submitting users home directory permissions bugfix ( OOZIE-3478 ) Coordinator/bundle libpath bugfix ( OOZIE-3415 ) Reducing Guava usage ( OOZIE-3521 ) Migrate from obsolete third party libraries (joda, commons-lang 2.x, commons-codec) Third party dependency revamp Thanks again Attila for pointing out the missing list. Best, Sala On Wed, Nov 13, 2019 at 10:00 AM Andras Salamon <[email protected]> wrote: > Hi Attila, > > New features: Sorry I missed this, thanks for pointing out, I'll send the > list soon. > Java11: Oozie should compile with Java11. We still have a few test issues, > but compilation should work ( > https://issues.apache.org/jira/browse/OOZIE-3459 ) > Maven version: I have opened a jira ticket about this: > https://issues.apache.org/jira/browse/OOZIE-3557 Do you think this is a > blocker issue? > > Best, > Sala > > On Mon, Nov 11, 2019 at 10:53 PM Attila Sasvári <[email protected]> > wrote: > >> Update: using maven 3.6.2, I managed to build the distro with OpenJDK 8. >> Apache >> Maven 3.3.9 might be too old (we should document minimum maven version). >> >> On Mon, Nov 11, 2019 at 7: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 >> > >> >
