[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Abhishek Bafna (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857401#comment-15857401
 ] 

Abhishek Bafna commented on OOZIE-2778:
---

+1.

Thanks [~asasvari] for working on this. Thanks [~andras.piros] for the review.
Committed to master.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Fix For: 5.0.0
>
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-07.patch, OOZIE-2778-2.patch, 
> OOZIE-2778-3.patch, OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Attila Sasvari (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856982#comment-15856982
 ] 

Attila Sasvari commented on OOZIE-2778:
---

org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop failure is 
unrelated.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-07.patch, OOZIE-2778-2.patch, 
> OOZIE-2778-3.patch, OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856878#comment-15856878
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

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:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
{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: 1871
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)

.Tests failing with errors:
.  

{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/3631/

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-07.patch, OOZIE-2778-2.patch, 
> OOZIE-2778-3.patch, OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Abhishek Bafna (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856304#comment-15856304
 ] 

Abhishek Bafna commented on OOZIE-2778:
---

+1.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-2.patch, OOZIE-2778-3.patch, 
> OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856280#comment-15856280
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

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:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [core].
{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: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/3630/

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-2.patch, OOZIE-2778-3.patch, 
> OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Attila Sasvari (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855978#comment-15855978
 ] 

Attila Sasvari commented on OOZIE-2778:
---

[~abhishekbafna] you are right, I see

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-2.patch, OOZIE-2778-3.patch, 
> OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855967#comment-15855967
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-2.patch, OOZIE-2778-3.patch, 
> OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Attila Sasvari (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855959#comment-15855959
 ] 

Attila Sasvari commented on OOZIE-2778:
---

[~abhishekbafna] that was on purpose, I just want to re-trigger the QA job. I 
don't think that failures are related to the latest changes, but let me 
re-execute the test cases.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-06.patch, OOZIE-2778-2.patch, OOZIE-2778-3.patch, 
> OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-07 Thread Abhishek Bafna (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855905#comment-15855905
 ] 

Abhishek Bafna commented on OOZIE-2778:
---

[~asasvari] I am afraid the recent patch will also fail to apply because it 
contains the same diff twice like the earlier one. There are no new changes 
compared to the last one. I think you need to check the last failed UTs locally 
for the patch [^OOZIE-2778-05.patch]. Thanks.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-2.patch, OOZIE-2778-3.patch, OOZIE-2778-4.patch, OOZIE-2778-5.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-06 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854215#comment-15854215
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

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:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
.{color:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [server].
{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: 1868
.Tests failed: 2
.Tests errors: 10

.The patch failed the following testcases:

.  
testMemoryUsageAndSpeed(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
.  testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)

.Tests failing with errors:
.  
testSetExecutionStats_when_user_has_specified_stats_write_FALSE(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testSetExecutionStats_when_user_has_specified_stats_write_TRUE(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testEndWithoutConfiguration(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testMapReduceWithUberJarEnabled(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  testStreaming(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testStreamingConfOverride(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testSetMapredJobName(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  testMapReduce(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testMapReduceWithConfigClass(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
.  
testMapReduceWithCredentials(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)

{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}

{color:red}.   There is at least one warning, please check{color}

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

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

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-05.patch, 
> OOZIE-2778-

[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-06 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853815#comment-15853815
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-2.patch, 
> OOZIE-2778-3.patch, OOZIE-2778-4.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-05 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853171#comment-15853171
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-2.patch, 
> OOZIE-2778-3.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852791#comment-15852791
 ] 

Hadoop QA commented on OOZIE-2778:
--

Testing JIRA OOZIE-2778

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch, OOZIE-2778-2.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-04 Thread Attila Sasvari (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852786#comment-15852786
 ] 

Attila Sasvari commented on OOZIE-2778:
---

Thanks [~abhishekbafna], I applied your patch and tested 
- starting Oozie,
- basic things on the web UI (e.g. listing workflows),
- Rest API version + status with curl
- workflow submission.


> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-03 Thread Abhishek Bafna (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852653#comment-15852653
 ] 

Abhishek Bafna commented on OOZIE-2778:
---

Thanks [~asasvari] for working on this.

Though I still faced some issue and addeingexclusion of the {{jsp-api}} helped 
me. Please verify at your end and update the patch as required. Pasting a {{git 
diff}} of the additional changes on top of the current patch.

{noformat}
iff --git a/server/pom.xml b/server/pom.xml
index a336aa8..dae6594 100644
--- a/server/pom.xml
+++ b/server/pom.xml
@@ -89,6 +89,10 @@
 org.mortbay.jetty
 jetty-util
 
+
+javax.servlet.jsp
+jsp-api
+
 
 
 
@@ -125,6 +129,10 @@
 org.eclipse.jetty.aggregate
 jetty-all
 
+
+javax.servlet.jsp
+jsp-api
+
 
 
 
{noformat}



> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-02 Thread Attila Sasvari (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850418#comment-15850418
 ] 

Attila Sasvari commented on OOZIE-2778:
---

[~abhishekbafna], [~rkanter] Could you have a look? Many thanks.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OOZIE-2778) Copy only jetty.version related server dependencies to distro

2017-02-02 Thread Attila Sasvari (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850412#comment-15850412
 ] 

Attila Sasvari commented on OOZIE-2778:
---

Test failure is unrelated.

> Copy only jetty.version related server dependencies to distro 
> --
>
> Key: OOZIE-2778
> URL: https://issues.apache.org/jira/browse/OOZIE-2778
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2778-01.patch
>
>
> To compile JSP, org.eclipse.jdt.core is used (see 
> http://www.eclipse.org/jetty/documentation/9.2.20.v20161216/configuring-jsp.html#compiling-jsps).
> However, additional currently jasper libraries are copied to 
> embedded-oozie-server/dependency/ in the distro directory. It can cause 
> problems (e.g. NoSuchMethodException at runtime) if classes are loaded from 
> that jars. 
> Furthermore, transitive dependencies can pull in old jetty libraries (such as 
> jetty-util 6) that can cause runtime issues (at server startup).
> We can make sure with the maven assembly plugin that only jetty.version 
> related dependencies are copied to distro.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)