Neil Barsema

Sure! that would be great

Thanks for the prompt reaction, unfortunately there is no immediate change in behavior, it still throws the error without options to ignore. Perhaps some handling of the UI is needed.

I'll test that out

Modifying the git config does not seem to work.

I guess you could try removing (renaming) the cacerts file in the JRE (lib/security) that way no ssl connection will validate.

I tried the local config only (not sure where I should put the global config for Jgit to find) If I access the repository from source tree (a git UI...

@Phillipus Yes, exactly, I do *not* get the error in Sourcetree but do in Archi. with that exact config setting.

I agree with Sven, Besides I would not call adding exception blocks around logging calls a "hack" if you truly don't care wether the logging completes or not.

The exceptions are the fire alarm not logger. If you are not 'debugging' Logger will not log anything and therefore not fail. If you *are* debugging I would expect you...

I can understand you would have liked logger to fail silently in this particular instance, however in any other scenario software failing silently is a major paint to diagnose.