You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Dave Brosius (JIRA)" <ji...@apache.org> on 2015/05/23 00:50:17 UTC

[jira] [Resolved] (CASSANDRA-9410) Fix? jar conflict with ecj

     [ https://issues.apache.org/jira/browse/CASSANDRA-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Brosius resolved CASSANDRA-9410.
-------------------------------------
    Resolution: Fixed

committed to cassandra-2.2 as commit bb1f1310478eab19111d17ac5509bce498d98743

> Fix? jar conflict with ecj
> --------------------------
>
>                 Key: CASSANDRA-9410
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9410
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Hadoop
>            Reporter: Dave Brosius
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For: 2.2.0 rc1
>
>         Attachments: ecj_conflict.txt
>
>
> hadoop-core pulls in core-3.1.1.jar which is an older version of ecj-4.4.2 which is now used directly for UDFs. Thus there are package/class conflicts between the two, when both are present on the classpath (at present)
> Made changes to remove the older core-3.1.1 dependency, and now the hadoop code relies on ecj-4.4.2. Code compiles, but not sure what needs to be done to validate the hadoop still works properly now only relying on ecj-4.4.2



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