accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1223) Mortbay/Jetty logging goes to console for VFS tests
Date Wed, 18 Mar 2015 19:54:38 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367772#comment-14367772
] 

Christopher Tubbs commented on ACCUMULO-1223:
---------------------------------------------

So, I actually don't even see slf4j-nop used in accumulo-start in master. I do, however, see
slf4j-log4j12 as a transitive dependency of hadoop-client and hadoop-minicluster (it's in
almost every hadoop artifact, actually... ; it'd be nice if Hadoop marked it as an optional
dependency so it didn't propagate automatically.).

Does this even matter, though, since it's just test output and it's being redirected to a
file and safely ignored? (I guess that's sort of what I was getting at when I asked if it
was still valid; I think this issue was created before we redirected console output in tests
to a file)

We could jump through hoops to exclude it from all our test dependencies, and add a test dependency
on slf4j-nop, but I'm not sure what is to be gained from that (especially since we already
have a direct dependency on log4j in accumulo-start; see ACCUMULO-3544).

> Mortbay/Jetty logging goes to console for VFS tests
> ---------------------------------------------------
>
>                 Key: ACCUMULO-1223
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1223
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: start
>            Reporter: Josh Elser
>            Priority: Minor
>              Labels: newbie
>
> My understanding leads me to think that since we include the slf4j-nop jar in accumulo-start,
this should send all of that logging to /dev/null.
> But, this isn't happening, so I have no idea what it's doing. Maybe switching it for
the slf4j-logj4 artifact and solely relying on log4j to manage it?



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

Mime
View raw message