The main hurdle for my day job is that Java 11 is not supported on all hardware platforms yet, specifically, some of our customers run our apps on IBM i/Series. That should not stop Log4j 3 to require Java 11 of course. It's just one data point. To make the migration even slower, even when Java 11 makes it to the i/Series, that will require some OS level that not everyone will be using, but it's too early for worry about that yet.
Gary On Sat, Nov 7, 2020 at 6:38 PM Ralph Goers <ralph.go...@dslextreme.com> wrote: > One of the goals for 3.0 is to have it fully support the Java Platform > Module System. Currently, we are required to have a java 8 project and a > java 9 project and merge them. If we say that 3.0 will only support Java > 11+ then we can get rid of these extra projects and add module-info.java to > all of the projects. > > Of course, we can continue development of the 2.x versions for as long as > we want to continue to support Java 8 (which I believe will be quite a > while yet. https://www.jrebel.com/blog/2020-java-technology-report, > https://snyk.io/wp-content/uploads/jvm_2020.pdf, and > https://www.jetbrains.com/lp/devecosystem-2020/java/ all indicate that > well over 50% of applications are using Java 8). > > Thoughts? > > Ralph >
