[
https://issues.apache.org/jira/browse/HTRACE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876553#comment-14876553
]
Hudson commented on HTRACE-256:
-------------------------------
SUCCESS: Integrated in HTrace-Master #115 (See
[https://builds.apache.org/job/HTrace-Master/115/])
HTRACE-256 addendum. Subprojects must rely on htrace-core4, not htrace-core
(cmccabe: rev b484809209edc3ea5d8ce3eacead57ee0898a5c5)
* htrace-htraced/pom.xml
* htrace-hbase/pom.xml
* htrace-zipkin/pom.xml
* htrace-webapp/pom.xml
* htrace-flume/pom.xml
> 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
> 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)
