Build failed in Jenkins: POI » POI-DSL-1.23 #44

2024-11-10 Thread Apache Jenkins Server
See Changes: [PJ Fanning] prep v5.4.0 [PJ Fanning] add since tags [Tim Allison] [bug-69434] -- add more properties to AttachmentChunks [PJ Fanning] upgrade spotbugs [PJ Fanning] xmlsec 3.0.5 [PJ Fanning

Re: [VOTE] Release Apache POI 5.4.0 (RC1)

2024-11-10 Thread PJ Fanning
Let's see what happens with apache/logging-log4j2/issues/3196. I don't see any tidy workaround in POI. We may just need to release note this. On 2024/11/10 11:31:00 Dominik Stadler wrote: > See https://github.com/apache/logging-log4j2/issues/3196 for details. > > Seems having a combination of l

Build failed in Jenkins: POI » POI-DSL-Windows-1.22 #62

2024-11-10 Thread Apache Jenkins Server
See Changes: [PJ Fanning] prep v5.4.0 [PJ Fanning] add since tags [Tim Allison] [bug-69434] -- add more properties to AttachmentChunks [PJ Fanning] upgrade spotbugs [PJ Fanning] xmlsec 3.0.5 [PJ

Re: [VOTE] Release Apache POI 5.4.0 (RC1)

2024-11-10 Thread Dominik Stadler
See https://github.com/apache/logging-log4j2/issues/3196 for details. Seems having a combination of log4j-api:2.24.1 and log4j-core:2.24.0 is broken, but we likely end up in such situations. Downgrading log4j-api to 2.24.0 for now would avoid running into this for now. Should we re-spin the relea

Re: [VOTE] Release Apache POI 5.4.0 (RC1)

2024-11-10 Thread Dominik Stadler
Hi, I started to test a bit with the RC, I see a strange problem related to Log4j, the static getLogger() returns null when using POI 5.4.0 and Log4j 2.24.0 in a sample project. When updating Log4j to 2.24.1, it works again. So sounds like a regression in Log4j 2.24.1 when combined with 2.24.0,