Hi all, The `log4j-flume-ng` module _de facto_ contains 3 different appenders:
* an Avro appender, that only depends on Avro and Avro IPC. Since it only communicates with Flume via network, it doesn't need to even depend on Flume, it just needs to use the same protocol. * a Persistent appender, which works the same way as Avro appender, but stores the messages to a local database first. It has an additional dependency on `je` (a mostly unmaintained implementation of BerkeleyDB). * an Embedded appender, which is the only one that actually depends on Flume. It also contains an undocumented (and untested) `Log4jEventSource` plugin for Flume. The use of optional dependencies is not very JPMS friendly and we probably would need to split it into 3 modules. To prevent delays in releasing 3.0.0 I would propose to: * either move the `log4j-flume-ng` module to a separate repo and release version `3.0.0` together with the next Flume release. * or move it from the `main` branch to a different branch that will be merged, when the module is ready. What do you think? Piotr
