This vote has passed with +1 votes from Matt Sicker, Remko Popma, and Ralph
Goers. I will continue with the release process.
Ralph
Here is my +1
Ralph
> On Jun 30, 2022, at 4:30 AM, Remko Popma wrote:
>
> +1 sigs good
>
> On Thu, Jun 30, 2022 at 8:23 PM Gary Gregory wrote:
>
>> I just ran it again and I get the same error, so I can't validate the
>> build for now.
>>
>> Gary
>>
>> On Wed, Jun 29, 2022 at 9:25 PM Matt
rgoers commented on PR #20:
URL: https://github.com/apache/logging-log4j1/pull/20#issuecomment-1172823709
As Ceki stated, Log4j 1.x has been EOL since 2015 and does not accept pull
requests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
rgoers closed pull request #20: [SECURITY] Use HTTPS to resolve dependencies in
Maven Build
URL: https://github.com/apache/logging-log4j1/pull/20
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
ceki commented on PR #20:
URL: https://github.com/apache/logging-log4j1/pull/20#issuecomment-1172712165
Thank you for this submission. Please note that log4j1 is no longer
maintained. In addition, [reload4j ](https://reload4j.qos.ch) which revives
log4j1, does not suffer from this issue.
JLLeitschuh opened a new pull request, #20:
URL: https://github.com/apache/logging-log4j1/pull/20
[](https://medium.com/@jonathan.leitschuh/want-to-take-over-the-java-ecosystem-
