[
https://issues.apache.org/jira/browse/CRUNCH-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824611#comment-13824611
]
Josh Wills commented on CRUNCH-295:
-----------------------------------
An update: I have an RC for 0.8.1 in the works, but I can't close the nexus
staging repo-- whenever I try, I get a 502 proxy error. Some googling indicates
that it could be b/c my public key isn't available (but it looks to me like it
is, see below); or it may be that Apache's infrastructure is just having some
proxy errors in general (there seem to be a lot of tickets along those lines in
INFRA right now, although I'm not sure if they're all related.)
My code keys up on MIT's key server:
http://pgp.mit.edu:11371/pks/lookup?search=jwills%40apache&op=index
> java.lang.IncompatibleClassChangeError: Found class
> org.apache.hadoop.mapreduce.TaskInputOutputContext, but interface was
> expected in crunch 0.8.0
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CRUNCH-295
> URL: https://issues.apache.org/jira/browse/CRUNCH-295
> Project: Crunch
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Stefan De Smit
> Assignee: Josh Wills
>
> Crunch 0.8.0 does not work for me, while crunch 0.7.0 did.
> To be more precise: when I compile crunch 0.8.0 from the git tag, it does
> work, but the jars downloaded from Maven Central don't.
> I compared both jars (mine vs downloaded) and they are indeed different.
> you can see (for instance in CrunchTaskContext):
> invokevirtual #4; //Method org/apache/hadoop/mapreduce...
> vs
> invokeinterface #4, 1; //InterfaceMethod org/apache/hadoop/mapreduce...
> Which means that crunch 0.8.0 is compiled with an interface iso an abstract
> class.
> the hadoop-1 profile shows a dependency to hadoop 1.1.2 which contains a
> class iso an interface.
> What we think happened is this:
> 1) compile crunch with hadoop-2 profile:
> 2) on same machine also compile crunch with hadoop-1 profile, but without
> clean option.
> because of the missing clean, maven won't recompile unchanged classes. which
> would explain how you end up with crunch 0.8.0 being compiled against
> hadoop-2 instead of hadoop-1
--
This message was sent by Atlassian JIRA
(v6.1#6144)
