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

Posted to dev@flume.apache.org by "E. Sammer (Closed) (JIRA)" <ji...@apache.org> on 2011/12/30 00:59:30 UTC

[jira] [Closed] (FLUME-913) slf4j-log4j binding is excluded from the dist assembly due to test scope

     [ https://issues.apache.org/jira/browse/FLUME-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

E. Sammer closed FLUME-913.
---------------------------

    
> slf4j-log4j binding is excluded from the dist assembly due to test scope
> ------------------------------------------------------------------------
>
>                 Key: FLUME-913
>                 URL: https://issues.apache.org/jira/browse/FLUME-913
>             Project: Flume
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: v1.0.0
>            Reporter: E. Sammer
>            Assignee: E. Sammer
>            Priority: Blocker
>             Fix For: v1.0.0
>
>
> It turns out that the slf4j-log4j binding was not properly included in the dist assembly even though it was listed in flume-ng-node as a compile scope dep. Upon investigation, it turns out that because it was listed in flume-ng-core as a test scope dep, it was excluded in the final artifact. Seems like a reactor dep bug. The short term work around is to remove the test scope from flume-ng-core.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira