[
https://issues.apache.org/jira/browse/SQOOP-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329742#comment-14329742
]
ASF subversion and git services commented on SQOOP-2120:
--------------------------------------------------------
Commit 62a5e8baad8e59b189828dad0dd0634fc84f3afb in sqoop's branch
refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=62a5e8b ]
SQOOP-2120: Sqoop2: Test classes using powermock fails badly when compiling
with java target version 1.7
(Jarek Jarcec Cecho via Abraham Elmahrek)
> 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)
