[
https://issues.apache.org/jira/browse/FLUME-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177466#comment-13177466
]
Hudson commented on FLUME-913:
------------------------------
Integrated in flume-728 #89 (See [https://builds.apache.org/job/flume-728/89/])
FLUME-913: slf4j-log4j binding is excluded from the dist assembly due to
test scope
esammer : http://svn.apache.org/viewvc/?view=rev&rev=1225698
Files :
* /incubator/flume/branches/flume-728/flume-ng-core/pom.xml
> 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