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 (Created) (JIRA)" <ji...@apache.org> on 2011/12/29 23:14:31 UTC
[jira] [Created] (FLUME-913) slf4j-log4j binding is excluded from
the dist assembly due to test scope
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
[jira] [Closed] (FLUME-913) slf4j-log4j binding is excluded from
the dist assembly due to test scope
Posted by "E. Sammer (Closed) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (FLUME-913) slf4j-log4j binding is excluded from
the dist assembly due to test scope
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (FLUME-913) slf4j-log4j binding is excluded from
the dist assembly due to test scope
Posted by "E. Sammer (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
E. Sammer resolved FLUME-913.
-----------------------------
Resolution: Fixed
Committed to flume-728.
> 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
[jira] [Commented] (FLUME-913) slf4j-log4j binding is excluded from
the dist assembly due to test scope
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177462#comment-13177462 ]
jiraposter@reviews.apache.org commented on FLUME-913:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3333/#review4157
-----------------------------------------------------------
Ship it!
+1
- Arvind
On 2011-12-29 22:16:22, Eric Sammer wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/3333/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-12-29 22:16:22)
bq.
bq.
bq. Review request for Flume.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Removed test scope from slf4j-log4j dep in flume-ng-core.
bq.
bq.
bq. This addresses bug FLUME-913.
bq. https://issues.apache.org/jira/browse/FLUME-913
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. flume-ng-core/pom.xml e4fb829
bq.
bq. Diff: https://reviews.apache.org/r/3333/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Eric
bq.
bq.
> 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
[jira] [Commented] (FLUME-913) slf4j-log4j binding is excluded from
the dist assembly due to test scope
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177426#comment-13177426 ]
jiraposter@reviews.apache.org commented on FLUME-913:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3333/
-----------------------------------------------------------
Review request for Flume.
Summary
-------
Removed test scope from slf4j-log4j dep in flume-ng-core.
This addresses bug FLUME-913.
https://issues.apache.org/jira/browse/FLUME-913
Diffs
-----
flume-ng-core/pom.xml e4fb829
Diff: https://reviews.apache.org/r/3333/diff
Testing
-------
Thanks,
Eric
> 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