Bump build requirement to JDK 11+
Hi all, I have merged PR#1369[1] and bumped the requirement for the JDK used to build `2.x` to JDK 11+, which is able to compile all our modules. If your JAVA_HOME points to a JDK 8 installation, you'll get a build failure. On the other hand Maven Toolchains are no longer required, unless you want to run your tests on JRE 8, in which case: * configure a JDK 8 toolchain, * run `./mvnw verify -Pjava8-tests` Of course the whole building instructions are available in our BUILDING.md[2]. Piotr PS: If you use JDK 17 you'll get a bunch of failing tests. I didn't want to waste time fixing them, since we'll probably fix them properly in a couple of months. [1] https://github.com/apache/logging-log4j2/pull/1369 [2] https://github.com/apache/logging-log4j2/blob/2.x/BUILDING.md
Re: Bump build requirement to JDK 11+
Hi Piotr, If Java 11 is the minimum requirement, the why is 8 still listed in .github/workflows/log4j-kafka-test.yml in the PR? Gary On Fri, Aug 4, 2023, 3:35 AM Piotr P. Karwasz wrote: > Hi all, > > I have merged PR#1369[1] and bumped the requirement for the JDK used > to build `2.x` to JDK 11+, which is able to compile all our modules. > If your JAVA_HOME points to a JDK 8 installation, you'll get a build > failure. > > On the other hand Maven Toolchains are no longer required, unless you > want to run your tests on JRE 8, in which case: > * configure a JDK 8 toolchain, > * run `./mvnw verify -Pjava8-tests` > > Of course the whole building instructions are available in our > BUILDING.md[2]. > > Piotr > > PS: If you use JDK 17 you'll get a bunch of failing tests. I didn't > want to waste time fixing them, since we'll probably fix them properly > in a couple of months. > > [1] https://github.com/apache/logging-log4j2/pull/1369 > [2] https://github.com/apache/logging-log4j2/blob/2.x/BUILDING.md >
Re: Bump build requirement to JDK 11+
Hi Gary, On Fri, 4 Aug 2023 at 12:43, Gary Gregory wrote: > If Java 11 is the minimum requirement, the why is 8 still listed > in .github/workflows/log4j-kafka-test.yml in the PR? I'll check for comments referring to JDK 8 tonight. JDK 8 is still used by the build system to run tests: there are at least a couple of tests that only run on JRE 8. Piotr
New design for the website
Hi all, Since our website has seen better times, I asked a young designer, Daniel Żabiński, to freshen it up a little bit. The preliminary sketches are available at: https://xd.adobe.com/view/455b5d92-d89b-45d9-984c-871974460249-1008/?fullscreen Personally I like the way it looks and I think we should implement it. This brings a lot of technical questions like: * do we even care about Maven Site skins or should we use a different static site generator? * Daniel proposes a nice "Search" feature, which technology can we use on a statically generated site? * can we have some dynamic content backed up by Apache infrastructure? * In the near future we'll be implementing a configuration validation tool. I would like to use the same Javascript library for both the tool and the rest of the website? What JS library would you propose for interactive content. Piotr
Re: New design for the website
Great initiative Piotr! Thank you. One requirement I'd like to request is that this looks decent on mobile, which it does not ATM, at least on Chrome and Android 13. Gary On Fri, Aug 4, 2023, 4:53 PM Piotr P. Karwasz wrote: > Hi all, > > Since our website has seen better times, I asked a young designer, > Daniel Żabiński, to freshen it up a little bit. > > The preliminary sketches are available at: > > > https://xd.adobe.com/view/455b5d92-d89b-45d9-984c-871974460249-1008/?fullscreen > > Personally I like the way it looks and I think we should implement it. > > This brings a lot of technical questions like: > * do we even care about Maven Site skins or should we use a different > static site generator? > * Daniel proposes a nice "Search" feature, which technology can we > use on a statically generated site? > * can we have some dynamic content backed up by Apache infrastructure? > * In the near future we'll be implementing a configuration validation > tool. I would like to use the same Javascript library for both the > tool and the rest of the website? What JS library would you propose > for interactive content. > > Piotr >
Re: New design for the website
In general I like the direction of this. The site is much more colorful. However… 1. I really think we should have a separate web site for the log4j api. 2. The manual needs much more than just being made pretty. Ralph > On Aug 4, 2023, at 1:53 PM, Piotr P. Karwasz wrote: > > Hi all, > > Since our website has seen better times, I asked a young designer, > Daniel Żabiński, to freshen it up a little bit. > > The preliminary sketches are available at: > > https://xd.adobe.com/view/455b5d92-d89b-45d9-984c-871974460249-1008/?fullscreen > > Personally I like the way it looks and I think we should implement it. > > This brings a lot of technical questions like: > * do we even care about Maven Site skins or should we use a different > static site generator? > * Daniel proposes a nice "Search" feature, which technology can we > use on a statically generated site? > * can we have some dynamic content backed up by Apache infrastructure? > * In the near future we'll be implementing a configuration validation > tool. I would like to use the same Javascript library for both the > tool and the rest of the website? What JS library would you propose > for interactive content. > > Piotr
