[
https://issues.apache.org/jira/browse/CASSANDRA-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724240#comment-13724240
]
Vijay commented on CASSANDRA-5826:
----------------------------------
Probably have to change the build.xml to copy the trigger directory to build
like what we do with conf directory?
I will add the above and also add it to Debian package may be (in addition
adding a property to override the trigger absolute path).
> 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
>
> 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
