You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/02/27 23:44:05 UTC

[jira] [Created] (ACCUMULO-3631) Exclude 'slf4j' artifacts from classpath in default value for general.classpaths

Josh Elser created ACCUMULO-3631:
------------------------------------

             Summary: Exclude 'slf4j' artifacts from classpath in default value for general.classpaths
                 Key: ACCUMULO-3631
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3631
             Project: Accumulo
          Issue Type: Bug
    Affects Versions: 1.6.2, 1.6.1, 1.6.0
            Reporter: Josh Elser
            Assignee: Josh Elser
             Fix For: 1.7.0, 1.6.3


Was testing out some Ambari integration for Accumulo that [~billie.rinaldi] and [~mwaineo] have been working on (AMBARI-5265) and found that, despite accumulo-site.xml having jars starting with slf4j excluded from the classpath, the shell would complain about duplicate slf4j-log4j12 jars on the classpath.

Turns out, because access to accumulo-site.xml was restricted (and we only had client.conf to use), we fell back on the default value for general.classpaths defined in AccumuloClassLoader. A short-term fix is to update the value there to match what's in our site template.

I'll add another issue for a long term fix to add classpath support to client configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)