[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15661444#comment-15661444 ] Attila Sasvari commented on OOZIE-2666: --- Thanks for the review [~rkanter], [~pbacsko], [~andras.piros]! > 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 > Fix For: trunk > > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.patch, > OOZIE-2666.PATCH-25.patch, OOZIE-2666.PATCH-27.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660251#comment-15660251 ] Robert Kanter commented on OOZIE-2666: -- +1 > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.patch, > OOZIE-2666.PATCH-25.patch, OOZIE-2666.PATCH-27.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651727#comment-15651727 ] 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 characters .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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: 1828 {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/3426/ > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.patch, > OOZIE-2666.PATCH-25.patch, OOZIE-2666.PATCH-27.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649061#comment-15649061 ] Hadoop QA commented on OOZIE-2666: -- Testing JIRA OOZIE-2666 Cleaning local git workspace {color:red}-1{color} Patch failed to apply to head of branch > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.patch, > OOZIE-2666.PATCH-25.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609902#comment-15609902 ] 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 characters .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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: 1825 {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/3412/ > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609756#comment-15609756 ] 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 characters .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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: 1825 {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/3411/ > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609203#comment-15609203 ] 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 characters .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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:red}-1 TESTS{color} .Tests run: 1825 .Tests failed: 0 .Tests errors: 1102 .The patch failed the following testcases: . {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/3410/ > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch, > OOZIE-2666.PATCH-23.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605939#comment-15605939 ] 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 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 2 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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: 1822 {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/3408/ > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602846#comment-15602846 ] 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 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 2 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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:red}-1 TESTS{color} .Tests run: 1822 .Tests failed: 1 .Tests errors: 1 .The patch failed the following testcases: . testTimeOutWithUnresolvedMissingDependencies(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand) {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/3405/ > 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, OOZIE-2666.PATCH-20.patch, > OOZIE-2666.PATCH-21.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15590429#comment-15590429 ] 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 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting. {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/3400/ > 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, OOZIE-2666.PATCH-20.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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586782#comment-15586782 ] Attila Sasvari commented on OOZIE-2666: --- I just re-tested the latest patch again on a Kerberized Hadoop cluster (using CDH) that it I can submit & execute workflows: tested with a simple mapreduce demo workflow and also with shell actions (with one that fails on purpose and also with another one that succeeds). [~jaydeepvishwakarma], [~rohini] could you please also have a quick look at the patch on ReviewBoard? I am wondering if you can spot functionality that is missing (i.e. additional jetty capabilities that can be important to configure and / or additional relevant HTTP / HTTPS settings) or some problems with the packaging part /approach (that is an area that I think still needs improvements). I tried to move a number Oozie configuration variables that are currently required to be passed via system properties to oozie-site/oozie-default.xml, but there are some that needs more refactoring. > 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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15578415#comment-15578415 ] 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 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15578247#comment-15578247 ] 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 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {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/3389/ > 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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15578071#comment-15578071 ] 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:red}-1{color} the patch contains 13 line(s) with 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 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {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/3388/ > 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 > > > 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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15577990#comment-15577990 ] 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:red}-1{color} the patch contains 13 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {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 warnings {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/3387/ > 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 > > > 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 (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15577804#comment-15577804 ] 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:red}-1{color} the patch contains 13 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:green}+1{color} the patch does not seem to introduce new javac warnings {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:red}-1 TESTS{color} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails 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/3386/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575561#comment-15575561 ] 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:red}-1{color} the patch contains 13 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{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 warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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/3383/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573451#comment-15573451 ] 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:red}-1{color} the patch contains 13 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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/3382/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572804#comment-15572804 ] Hadoop QA commented on OOZIE-2666: -- Testing JIRA OOZIE-2666 Cleaning local git workspace {color:red}-1{color} Patch failed to apply to head of branch > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572796#comment-15572796 ] Hadoop QA commented on OOZIE-2666: -- Testing JIRA OOZIE-2666 Cleaning local git workspace {color:red}-1{color} Patch failed to apply to head of branch > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572269#comment-15572269 ] Hadoop QA commented on OOZIE-2666: -- Testing JIRA OOZIE-2666 Cleaning local git workspace {color:red}-1{color} Patch failed to apply to head of branch > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1628#comment-1628 ] 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:red}-1{color} the patch contains 13 line(s) with 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 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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/3363/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15554615#comment-15554615 ] 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:red}-1{color} the patch contains 12 line(s) with 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 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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/3361/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553660#comment-15553660 ] 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:red}-1{color} the patch contains 2 line(s) with trailing spaces .{color:red}-1{color} the patch contains 9 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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/3360/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535906#comment-15535906 ] 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:red}-1{color} the patch contains 2 line(s) with trailing spaces .{color:red}-1{color} the patch contains 12 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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: 1820 {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/3352/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535787#comment-15535787 ] 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:red}-1{color} the patch contains 2 line(s) with trailing spaces .{color:red}-1{color} the patch contains 12 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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: 1820 {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/3351/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533523#comment-15533523 ] 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:red}-1{color} the patch contains 2 line(s) with trailing spaces .{color:red}-1{color} the patch contains 12 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 2 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 3 new javac warning(s) {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:red}-1 TESTS{color} .Tests run: 1814 .Tests failed: 0 .Tests errors: 2 .The patch failed the following testcases: . {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/3342/ > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie
[ https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533300#comment-15533300 ] Robert Kanter commented on OOZIE-2666: -- [~asasvari], thanks for working on this! Can you upload the patch to ReviewBoard? That will make it easier to review. > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)