[
https://issues.apache.org/jira/browse/FLUME-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636164#comment-13636164
]
Mike Percy commented on FLUME-2008:
-----------------------------------
Roman, thanks for the patch!
I wasn't sure about the Maven-fu to achieve this. However I wonder if the lib
directory is the right place to put this? The bin/flume-ng script pulls in all
the jars in lib/* for the agent classpath. People would need to know to delete
this jar if they want to override certain other jar dependencies in their own
deployments, just as one example of the confusion this could create.
Worth noting that I want to do a similar thing for some load testing tools that
I have had lying around (but I also want that to be an executable jar). Anyway
I think this should go in but I feel like we should create a special place for
these little buggers.
> it would be very convenient to have a fat jar of flume-ng-log4jappender
> -----------------------------------------------------------------------
>
> Key: FLUME-2008
> URL: https://issues.apache.org/jira/browse/FLUME-2008
> Project: Flume
> Issue Type: Improvement
> Components: Client SDK
> Affects Versions: v1.3.1
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: v1.4.0
>
> Attachments: FLUME-2008.patch.txt
>
>
> It would be extremely convenient to have a single fat jar of
> flume-ng-log4jappender so that it can be added to the classpath of a
> particular log4j consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
