[
https://issues.apache.org/jira/browse/CASSANDRA-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928771#action_12928771
]
paul cannon commented on CASSANDRA-1689:
----------------------------------------
as a debian packager and ops guy, I strongly recommend allowing additions to
the classpath in /etc/default/cassandra. that file is already sourced in the
initscript if it exists, but it can't do anything as is to affect the classpath
generation. /etc/default is well
you don't want to inherit a global CLASSPATH, that probably isn't terribly
useful.
it would also make sense for the initscript to look explicitly for jna.jar,
mx4j-tools.jar, and other non-bundled libs in their standard places by OS, so
the admin doesn't need to do anything extra for those cases.
i'll send a patch for the Debian initscript, at least, in a bit.
> avoid nuking system classpath
> -----------------------------
>
> Key: CASSANDRA-1689
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1689
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Reporter: Jonathan Ellis
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.7.1
>
>
> this will allow using system packages for jna on debian and redhat
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
