[
https://issues.apache.org/jira/browse/ACCUMULO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938262#comment-14938262
]
Christopher Tubbs edited comment on ACCUMULO-4014 at 9/30/15 6:52 PM:
----------------------------------------------------------------------
Yes, it would make me happy, but I'm not sure when we'll be able to get there.
Specifically, I'd love to be able to launch any Accumulo service or client with
little more than setting {{$CLASSAPATH}} and calling {{java <serviceMainClass>
-D<serviceName>.config=<configFileLocation>}} (making it really easy to write
simple wrapper scripts, like those in {{rpm -E %jpackage_script}}).
Complicating the situation is the extended VFS classloader, and the context
classloading. If we strip out accumulo-start, we'll probably have to implement
those things by another means.
was (Author: ctubbsii):
Yes, it would make me happy, but I'm not sure when we'll be able to get there.
Specifically, I'd love to be able to launch any Accumulo service or client with
little more than setting {{$CLASSAPATH}} and calling {{java <serviceMainClass>
-D<serviceName>.config=<configFileLocation>}}.
Complicating the situation is the extended VFS classloader, and the context
classloading. If we strip out accumulo-start, we'll probably have to implement
those things by another means.
> cannot extend classpath in accumulo-env.sh
> ------------------------------------------
>
> Key: ACCUMULO-4014
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4014
> Project: Accumulo
> Issue Type: Improvement
> Components: scripts
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Trivial
>
> I wanted to add a new log4j appender for accumulo processes.
> The jars to support this appender need to be provided before the start jar
> does its magic and configures the longer classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
