[GitHub] [logging-log4j1] JLLeitschuh commented on pull request #21: [SECURITY] Use HTTPS to resolve dependencies in Maven Build

JLLeitschuh commented on PR #21: URL: https://github.com/apache/logging-log4j1/pull/21#issuecomment-1185166905 Please forgive me. Do consider archiving the project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

[GitHub] [logging-log4j1] rgoers commented on pull request #21: [SECURITY] Use HTTPS to resolve dependencies in Maven Build

rgoers commented on PR #21: URL: https://github.com/apache/logging-log4j1/pull/21#issuecomment-1185142283 @JLLeitschuh Please stop creating duplicate PRs -- 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

[GitHub] [logging-log4j1] garydgregory closed pull request #21: [SECURITY] Use HTTPS to resolve dependencies in Maven Build

garydgregory closed pull request #21: [SECURITY] Use HTTPS to resolve dependencies in Maven Build URL: https://github.com/apache/logging-log4j1/pull/21 -- 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 t

[GitHub] [logging-log4j1] garydgregory commented on pull request #21: [SECURITY] Use HTTPS to resolve dependencies in Maven Build

garydgregory commented on PR #21: URL: https://github.com/apache/logging-log4j1/pull/21#issuecomment-1185094237 Closing: version 1.x is EOL. -- 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 sp

[GitHub] [logging-log4j1] JLLeitschuh opened a new pull request, #21: [SECURITY] Use HTTPS to resolve dependencies in Maven Build

JLLeitschuh opened a new pull request, #21: URL: https://github.com/apache/logging-log4j1/pull/21 [](https://medium.com/@jonathan.leitschuh/want-to-take-over-the-java-ecosystem-

Re: Dependencies for `log4j-jakarta-smtp`

I kind of like Matt's solution of just telling people to exclude those artifacts when they don't need them. Otherwise we'll have the same issue in reverse: requests from people about how to include the "missing" dependencies On Thu, Jul 14, 2022 at 8:56 PM Piotr P. Karwasz wrote: > Hi Tim, >

Re: Dependencies for `log4j-jakarta-smtp`

Hi Tim, On Tue, 19 Apr 2022 at 19:32, Tim Perry wrote: > > Will including `com.sun.activation:jakarta.activation` and > `com.sun.mail:smtp` be a problem on application servers > that already include implementations of them? My > knowledge of the J2EE application servers is incomplete > for the m

Re: Need assistance regarding warning - Class path contains multiple SLF4J bindings

Hi Nilay, On Thu, 14 Jul 2022 at 09:36, Nilay Prafulla Dhamecha wrote: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/lib/slf4j-log4j12-1.7.31.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/lib/slf4j-simple-1.7.31

Need assistance regarding warning - Class path contains multiple SLF4J bindings

Hi, We have recently migrated our logging framework from log4j1.x to log4j2.17.1 Below are the jars we are using currently in our project. *Please note that we do not have a Mavan/Gradle based project, the dependencies are managed manually.* *Jars : * *log4j-api-2.17.1log4j-appserver-2.17.