[jira] [Commented] (SQOOP-2120) Sqoop2: Test classes using powermock fails badly when compiling with java target version 1.7

["Sqoop QA bot (JIRA)" <ji...@apache.org>]

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

Sqoop QA bot commented on SQOOP-2120:
-------------------------------------

Testing file [SQOOP-2120.patch|https://issues.apache.org/jira/secure/attachment/12699809/SQOOP-2120.patch] against branch sqoop2 took 0:40:16.267264.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} Patch does not add/modifny any test case
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All fast unit tests passed
{color:green}SUCCESS:{color} All slow unit tests passed
{color:green}SUCCESS:{color} All fast integration tests passed
{color:green}SUCCESS:{color} All slow integration tests passed

Console output is available [here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1088/console].

This message is automatically generated.

> Sqoop2: Test classes using powermock fails badly when compiling with java target version 1.7
> --------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-2120
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2120
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.5
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-2120.patch
>
>
> I've tried to change bytecode target version to 1.7 and found out that test classes using Powermock are failing quite badly with JDK error:
> {code}
> Bad <init> method call from inside of a branch
> {code}
> Doing a bit of googling turned out that this is a known problem where powermock is doing something fancy that is no longer supported in JDK7.
> * http://stackoverflow.com/questions/25428317/bad-init-method-call-from-inside-of-a-branch
> * https://code.google.com/p/powermock/issues/detail?id=504
> Recommendation on those sites is to either use {{-noverify}} JVM flag or force usage of the old verifier by specifying {{-XX:-UseSplitVerifier}}. I feel that the later is a better option, so I would propose to do that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)