[
https://issues.apache.org/jira/browse/CASSANDRA-16303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242402#comment-17242402
]
Michael Semb Wever commented on CASSANDRA-16303:
------------------------------------------------
git bisect shows e8b8a90336dfd7d8b3fe06d06fe6970ab3be5fa1 was the last commit
to have it, and
[4881d9c308ccd6b5ca70925bf6ebedb70e7705fc|https://github.com/apache/cassandra/commit/4881d9c308ccd6b5ca70925bf6ebedb70e7705fc#diff-766797f233c18114f9499750cf1ffbf3829aeea50283850619c01bd173132021L639]
removed the dependency from the all-pom.
This looks to have happened because it was originally incorrectly added in the
thrift-pom.
> ClassNotFoundException: com.googlecode.concurrenttrees.radix.node.NodeFactory
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-16303
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16303
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
> Reporter: Adrian Cole
> Priority: Normal
> Fix For: 4.0-beta
>
>
> If you look at the pom for cassandra-all 4.0.0-beta-3, you'll notice that
> concurrent-trees is in dependencyManagement, but not dependencies. This might
> be going unnoticed as sasi is disabled by default now, but it can lead to a
> ClassNotFoundException. I presume this was accidental
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
