[jira] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-11-09 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-27.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-26 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-24.patch

same as patch 23, retrigger QA 

(applying patch on 1bf91be7b3f824ca4a9fb3e705764574f5dae4da tests in 
org.apache.oozie.action.hadoop.TestJavaActionExecutor do not fail locally with 
JDK 8)

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-26 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: (was: OOZIE-2666.PATCH-23.patch)

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-26 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-23.patch

> 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-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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-26 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-23.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-25 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-22.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-24 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-21.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-19 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-20.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-19.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-18.patch

> 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
>
>
> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-17.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-16.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-15.patch

> 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
>
>
> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Description: 
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

  was:
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.



> 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.
> - 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-15 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-14.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-14 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-13.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-13 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-12.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-13 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-11.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-13 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-10.patch

rebase

> 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
>
>
> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-13 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-09.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-07 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-07.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-07 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-06.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-06 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-05.patch

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-09-30 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-03.patch

Refactor oozied.sh

> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-09-30 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-02.patch

- Change Jetty version to 9.2.19.v20160908 because Jetty 9.3 requires Java 8 
(see 
http://www.eclipse.org/jetty/documentation/current/what-jetty-version.html); no 
code changes were needed

> 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
>
>
> 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] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-09-29 Thread Attila Sasvari (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-01.patch

> 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)