merks commented on PR #337:
URL: https://github.com/apache/commons-logging/pull/337#issuecomment-2643355066
I can verify that in an environment with this problem:
```
java.lang.ExceptionInInitializerError
at
org.apache.http.conn.ssl.SSLConnectionSocketFactory.<clinit>(SSLConnectionSocketFactory.java:151)
at
org.eclipse.jgit.transport.http.apache.HttpClientConnectionFactory$HttpClientSession.configure(HttpClientConnectionFactory.java:89)
at
org.eclipse.jgit.transport.http.apache.HttpClientConnectionFactory$HttpClientSession.configure(HttpClientConnectionFactory.java:1)
at
org.eclipse.jgit.transport.TransportHttp.httpOpen(TransportHttp.java:1062)
at
org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:651)
at
org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:465)
at
org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:153)
at
org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:105)
at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1458)
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:238)
at org.eclipse.jgit.api.PullCommand.call(PullCommand.java:266)
at
org.eclipse.egit.core.op.PullOperation$PullJob.run(PullOperation.java:256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.apache.commons.logging.LogConfigurationException: The chosen
LogFactory implementation does not extend LogFactory. Please check your
configuration. (Caused by java.lang.ClassCastException: The application has
specified that a custom LogFactory implementation should be used but Class
'org.apache.commons.logging.impl.LogFactoryImpl' cannot be converted to
'org.apache.commons.logging.LogFactory'. The conflict is caused by the presence
of multiple LogFactory classes in incompatible classloaders. Background can be
found in http://commons.apache.org/logging/tech.html. If you have not
explicitly specified a custom LogFactory then it is likely that the container
has set one without your knowledge. In this case, consider using the
commons-logging-adapters.jar file or specifying the standard LogFactory from
the command line. Help can be found
@http://commons.apache.org/logging/troubleshooting.html.)
at
org.apache.commons.logging.LogFactory.createFactory(LogFactory.java:1154)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:960)
at
java.base/java.security.AccessController.doPrivileged(AccessController.java:319)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:957)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:624)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
at
org.apache.http.conn.ssl.AbstractVerifier.<init>(AbstractVerifier.java:61)
at
org.apache.http.conn.ssl.AllowAllHostnameVerifier.<init>(AllowAllHostnameVerifier.java:44)
at
org.apache.http.conn.ssl.AllowAllHostnameVerifier.<clinit>(AllowAllHostnameVerifier.java:46)
... 13 more
Caused by: java.lang.ClassCastException: The application has specified that
a custom LogFactory implementation should be used but Class
'org.apache.commons.logging.impl.LogFactoryImpl' cannot be converted to
'org.apache.commons.logging.LogFactory'. The conflict is caused by the presence
of multiple LogFactory classes in incompatible classloaders. Background can be
found in http://commons.apache.org/logging/tech.html. If you have not
explicitly specified a custom LogFactory then it is likely that the container
has set one without your knowledge. In this case, consider using the
commons-logging-adapters.jar file or specifying the standard LogFactory from
the command line. Help can be found
@http://commons.apache.org/logging/troubleshooting.html.
at
org.apache.commons.logging.LogFactory.createFactory(LogFactory.java:1108)
... 21 more
```
that updating to the new 1.3.5 version:
Allows me to do a pull again,
I.e., this change definitely fixes the problem we had with the 1.3.4 version.
Woo hoo! 🥇 💟
--
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 specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
