[Cyberduck-trac] [Cyberduck] #3641: java.lang.ExceptionInInitializerError (org.apache.commons.logging.LogConfigurationException: No suitable Log constructor)

[Cyberduck]

#3641: java.lang.ExceptionInInitializerError
(org.apache.commons.logging.LogConfigurationException: No suitable Log
constructor)
--------------------+-------------------------------------------------------
 Reporter:  samj    |        Owner:  dkocher   
     Type:  defect  |       Status:  closed    
 Priority:  normal  |    Milestone:            
Component:  core    |      Version:  3.2.1     
 Severity:  major   |   Resolution:  worksforme
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by samj):

 OK so the problem was that I had commons-logging-1.0.4.jar in
 /Library/Java/Extensions. Removing it allows Cyberduck to start but breaks
 other Java applications on my system. I did find however that downloading
 log4j from http://logging.apache.org/log4j/1.2/index.html and installing
 both commons-logging-1.0.4.jar and log4j-1.2.15.jar into
 /Library/Java/Extensions. That is to say it appears to be ok if you have
 commons-logging in your Java path provided you also have log4j?

 Note that it's a difficult problem to diagnose - initially Cyberduck would
 just crash on launch but then more recent versions I could see e.g. Amazon
 S3 connections but attempts to open them were silently ignored (unless I
 opened a terminal, ran
 /Applications/Cyberduck.app/Contents/MacOS/Cyberduck directly and watched
 for the errors on the command line. As I said, not a Java guru but I do
 wonder whether this condition couldn't be better handled (e.g. with a
 sensible error?).

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/3641#comment:8>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV, Cloud Files and Amazon S3 Browser for Mac OS X.