[
https://issues.apache.org/jira/browse/CASSANDRA-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727960#comment-13727960
]
Vijay commented on CASSANDRA-5826:
----------------------------------
{quote}
As long as we are not trying to isolate classloaders or anything
{quote}
Actually we do it with triggers, similar to what solr does for Tokenizer code
etc (but not the same).
For the record: You can place all of your dependencies in the trigger directory
except everything which Cassandra depends on.
If the user uses maven for building, all he needs to do is, and place the jars
in the trigger directory.
{code}
<dependency>
<groupId>org.apache.cassandra</groupId>
<artifactId>cassandra-all</artifactId>
<version>2.0.0-beta2</version>
<scope>provided</scope>
</dependency>
{code}
My understanding is that, Java doesn't do nested class path scanning on sub
directories, hence conf file was ok to do.
But understand it is kind of scary if someone places in conf instead.
> Fix trigger directory detection code
> ------------------------------------
>
> Key: CASSANDRA-5826
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5826
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0 beta 2
> Environment: OS X
> Reporter: Aleksey Yeschenko
> Assignee: Vijay
> Labels: triggers
> Fix For: 2.0 rc1
>
> Attachments: 0001-5826.patch
>
>
> At least when building from source, Cassandra determines the trigger
> directory wrong. C* calculates the trigger directory as 'build/triggers'
> instead of 'triggers'.
> FBUtilities.cassandraHomeDir() is to blame, and should be replaced with
> something more robust.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
