You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/02/20 05:05:11 UTC
[jira] [Created] (SQOOP-2120) Sqoop2: Test classes using powermock
fails badly when compiling with java target version 1.7
Jarek Jarcec Cecho created SQOOP-2120:
-----------------------------------------
Summary: 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
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)