Re: Plugin attribute constraint validation

2022-02-23 Thread Piotr P. Karwasz
Thank you both for your answers, which helped me solve the problems I have with constraint validation. Regarding Ralph's Log4j 1.x bridge validation: On Sun, Feb 20, 2022 at 9:46 PM Ralph Goers wrote: > I suspect if we simply extract the values and pass them to the Log4j 2 > component’s > Builde

RE: [Newsletter] Re: Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

2022-02-23 Thread Denis Petker
Hi there, @Vladimir: thanks for your thoughts. Unfortunately I cannot get around the issue by just tweaking the config. I tried all constellations fixing the UserName/Properties etc. Looking at the code confirmes, that it just always fetches the UserName from the System for each logging event,

[VOTE] Release Apache Log4j 2.17.2-rc1

2022-02-23 Thread Ralph Goers
This is a vote to release Log4j 2.17.2, the next version of the Log4j 2 project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours. All votes are welcome and we encourage ev

Re: [VOTE] Release Apache Log4j 2.17.2-rc1

2022-02-23 Thread Remko Popma
+1 Signatures good, checksums good. Build passes (ignoring rev-api problem for the mongodb3 module) Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-28T00:06:16+09:00) Maven home: C:\apps\apache-maven-3.6.2\bin\.. Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:

Re: [VOTE] Release Apache Log4j 2.17.2-rc1

2022-02-23 Thread Remko Popma
I noted that the checksum files for the distribution archives are now _almost_ in the right format to allow checking with the `shasum` utility: cat ./apache-log4j-2.17.2-bin.tar.gz.sha256 c8f7cfe4ac9825043432b310709dee2661398573de28c83e603e80e0e86df9bb apache-log4j-2.17.2-bin.tar.gz Unfortunately

Re: [VOTE] Release Apache Log4j 2.17.2-rc1

2022-02-23 Thread Matt Sicker
+1 Build good, sigs good, artifacts good. Site notes: * Markdown parsing errors on homepage with “##” instead of tags or whatever goes there. * API Separation page has an outdated version reference * Similar markdown parsing errors on the Log4j 1.x Migration page with “” being left as-is.

Re: [VOTE] Release Apache Log4j 2.17.2-rc1

2022-02-23 Thread Ralph Goers
I will take a look. I had thought I verified they had 2 spaces. Ralph > On Feb 23, 2022, at 7:54 PM, Remko Popma wrote: > > I noted that the checksum files for the distribution archives are now > _almost_ in the right format to allow checking with the `shasum` utility: > > cat ./apache-log4j-