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

Posted to issues@htrace.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/10/14 02:46:05 UTC

[jira] [Updated] (HTRACE-256) Change the artifactId for htrace-core in branch 4.0 to be htrace-core4

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

Colin Patrick McCabe updated HTRACE-256:
----------------------------------------
    Affects Version/s: 4.0
     Target Version/s: 4.0.1
          Component/s: core
                       build

> Change the artifactId for htrace-core in branch 4.0 to be htrace-core4
> ----------------------------------------------------------------------
>
>                 Key: HTRACE-256
>                 URL: https://issues.apache.org/jira/browse/HTRACE-256
>             Project: HTrace
>          Issue Type: Bug
>          Components: build, core
>    Affects Versions: 4.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 4.1, 4.0.1
>
>         Attachments: 256.patch
>
>
> Incompatible artifactId change so can have htrace 3.2 and htrace 4.0 on same CLASSPATH. Examples of where we need this are an hbase updated to use 4.0 APIs but using an HDFS that has the old APIs or, inside in htrace itself, the htrace-hbase module can't be updated to hbase 1.0.0 because hbase 1.0.0 is on htrace 3.2.
> With a different artifactId and different package names, no possibility of NoClassDefFound.



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