Based on the above, it seems that we have consensus to move forward with an ABI-breaking change and a Flume 2.0 release.
I'm going to branch from the current trunk as flume-1.x and we can continue committing to trunk assuming that the next release from trunk will be the 2.0.0 release. I'm also going to +1 Denes' change @ https://github.com/apache/ flume/pull/195 Mike On Tue, Jan 30, 2018 at 2:32 PM, Mike Percy <mpe...@apache.org> wrote: > On Tue, Jan 30, 2018 at 11:20 AM, Hari Shreedharan < > hshreedha...@apache.org> wrote: > >> Agreed. Another change we might want to consider is shading the >> dependencies of individual modules and the framework itself. This will >> make >> it easier to upgrade individual modules. >> > > +1, I don't know to what extent this is possible but if so then I'm all > for it. > > Mike > >