Java 9 is needed at compile time for the Java 9 support, but it is not required at run time.
On Wed, Feb 21, 2018 at 05:47, Andrejus Chaliapinas <andrej...@yahoo.com.invalid> wrote: > Thank you Matt for confirming. Could you or Ralph update that mentioned > Runtime Dependency page for v2.10.0 case, so no need for others to ask same > question? > Also from build perspective - I'm a bit confused about building current > Master branch as I can't find 2.11.0 I was looking for for mentioned issue > earlier. > BUILDING.md file from Master says:To build Log4j 2, you need a JDK > implementation version 1.7 or greater, JDK > version 9, and Apache Maven 3.x. > so it mentions 2 JDKs here. Is that correct? I've tried to build just > log4j-api and log4j-core parts with JDK 8, but since they both depend on > either log4j-api-java9 or log4j-core-java9 now - build fails for me as > toolchain for them requires JDK9. > If there is some different FAQ on building bits in addition to that > Runtime Dependencies page - please point me there. > Cheers,Andrejus > > On Tuesday, February 20, 2018 10:06 PM, Matt Sicker <boa...@gmail.com> > wrote: > > > Log4j 2.10 still requires Java 7. We're planning to require Java 8 only in > Log4j 3.x. The Java 9 support is so that if you're running in Java 9, you > can take advantage of modules and a couple alternative class > implementations due to new standard APIs ported from formerly internal JDK > APIs. > > On 20 February 2018 at 15:33, Andrejus Chaliapinas < > andrej...@yahoo.com.invalid> wrote: > > > Hi, > > Would it be possible on this dependencies page:https://logging.apache. > > org/log4j/2.0/runtime-dependencies.html > > to specify if v2.10.0 still works with Java 7 or 8 as stated for v2.9.1 > or > > mostly Java 9 is now targeted? And if there could be now some side > effects > > with Java 8 (like LOG4J2-2129) while Log4j2 code is progressing to Java 9 > > modules approach? > > > > Thank you,Andrejus > > > > > > -- > Matt Sicker <boa...@gmail.com> > > > -- Matt Sicker <boa...@gmail.com>
