I don’t think a major version change should be necessary just because the JDK 
dependency changed. Changing the major version number should tied to major 
changes in the project itself.

I am curious to know what dependencies now only run on Java 11.

Ralph

> On May 3, 2019, at 5:02 AM, Ferenc Szabo <szabofe...@apache.org> wrote:
> 
> Hello Flume devs
> 
> I was looking into the Java 11 support in Flume and some of the
> dependencies are not compatible with Java 11 and does not have compatible
> versions within the same major version.
> 
> Also, some of them have security vulnerabilities that have been fixed in
> another major version.
> 
> What do you think about updating dependencies to a higher major version and
> possibly losing some backward compatibility in 1.10? Or should we move to
> 2.0 with more effort and updating there? Also adding some framework changes
> that would enable us to implement things we could not do in a minor version.
> 
> We should create a roadmap for us containing library updates, new
> components and framework improvements.
> 
> Regards,
> Ferenc Szabo


Reply via email to