You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org> on 2011/12/24 21:40:31 UTC

[jira] [Commented] (FLUME-833) Audit Direct Library Deps for Flume NG

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

jiraposter@reviews.apache.org commented on FLUME-833:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3315/
-----------------------------------------------------------

Review request for Flume.


Summary
-------

* Updated all versions (where it didn't break compatibility).
* Updated plugin and dep management to include all versions.
* Removed explicit versions in modules.

Note that this is based on FLUME-902 because it dealt with thrift.


This addresses bug FLUME-833.
    https://issues.apache.org/jira/browse/FLUME-833


Diffs
-----

  c/flume-ng-core/pom.xml 2726b06 
  c/flume-ng-node/pom.xml a5a2ae5 
  c/pom.xml 3a177f0 

Diff: https://reviews.apache.org/r/3315/diff


Testing
-------


Thanks,

Eric


                
> Audit Direct Library Deps for Flume NG
> --------------------------------------
>
>                 Key: FLUME-833
>                 URL: https://issues.apache.org/jira/browse/FLUME-833
>             Project: Flume
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: NG alpha 1
>            Reporter: Will McQueen
>            Assignee: E. Sammer
>             Fix For: v1.0.0
>
>
> Need to audit all libs directly used by Flume NG at compile-time (static deps). Also include runtime deps that are invoked reflectively (eg, Derby driver and SLF4J binding to log4j).

--
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