Hadoop QA commented on OOZIE-2666:

Testing JIRA OOZIE-2666

Cleaning local git workspace


{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:red}-1{color} the patch contains 9 line(s) longer than 132 
.    {color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.    Tests run: 1821
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

{color:red}*-1 Overall result, please check the reported -1(s)*{color}

The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3390/

> Support embedding Jetty into Oozie
> ----------------------------------
>                 Key: OOZIE-2666
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2666
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Attila Sasvari
>            Assignee: Attila Sasvari
>         Attachments: OOZIE-2666.PATCH-01.patch, OOZIE-2666.PATCH-02.patch, 
> OOZIE-2666.PATCH-03.patch, OOZIE-2666.PATCH-05.patch, 
> OOZIE-2666.PATCH-06.patch, OOZIE-2666.PATCH-07.patch, 
> OOZIE-2666.PATCH-09.patch, OOZIE-2666.PATCH-10.patch, 
> OOZIE-2666.PATCH-11.patch, OOZIE-2666.PATCH-12.patch, 
> OOZIE-2666.PATCH-13.patch, OOZIE-2666.PATCH-14.patch, 
> OOZIE-2666.PATCH-15.patch, OOZIE-2666.PATCH-16.patch, 
> OOZIE-2666.PATCH-17.patch, OOZIE-2666.PATCH-18.patch, 
> OOZIE-2666.PATCH-19.patch
> The purpose of this task is to allow Oozie to run as a standalone application 
> rather than being deployed to a container inside a WAR file.
> - Build embedded jetty enabled Oozie by default
> - Allow building Tomcat based Oozie by specifying the 'tomcat' profile
> - Starting Oozie with oozied.sh detect webserver type based on the build info
> - Oozie Web UI is working with JDK 8 if using embedded jetty 
> - If using Jetty, allow the user to configure the following settings via 
> oozie-default / oozie-site xml:
> -- request / response header size
> -- allowed HTTPS protocols
> -- excluded / weak cipher suites
> -- threadpool size

This message was sent by Atlassian JIRA

Reply via email to