[
https://issues.apache.org/jira/browse/FLUME-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530185#comment-13530185
]
Mike Percy commented on FLUME-1735:
-----------------------------------
It what you are describing something like OSGi? The direction sounds like the
right way to go, to me, in the long term. In the short term, just starting off
with something that, as you say, adds certain subdirectories to the classpath
at startup time seems like a win.
> Add support for a plugins.d directory
> -------------------------------------
>
> Key: FLUME-1735
> URL: https://issues.apache.org/jira/browse/FLUME-1735
> Project: Flume
> Issue Type: Improvement
> Reporter: Mike Percy
> Assignee: Brock Noland
> Fix For: v1.4.0
>
>
> It would be nice to have a directory, called something like plugins.d, which
> had the following structure:
> {noformat}
> flume/
> bin/
> conf/
> lib/
> plugins.d/
> custom-source-1/
> custom-source-1-base.jar
> custom-source-1-ext.jar
> custom-interceptor-2/
> custom-interceptor-2-main.jar
> custom-interceptor-2-lib.jar
> {noformat}
> This would make it easy for users to easily install new plugins (sources,
> sinks, interceptors, etc) and in the case of some conflict, they can easily
> be differentiated and moved out of the include path. This helps with
> management and debugging of plugin issues, and avoids the current requirement
> for users to add these plugins to their FLUME_CLASSPATH.
--
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
