Exclude SLF4J from smbj since it causes class loading errors. #481
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I upgraded to 1.50.3 (from an ancient version which was no longer compatible with modern Jenkins), connections to Windows nodes started failing with no errors in any logs, which I traced to a NoClassDefFoundError caused by loading SLF4J classes from both the plugin and Jenkins itself. The lack of logging remains, but excluding SLF4J from the SMBJ dependency fixes the problem for me. I have no idea if this is the right solution, though.
This may be what's causing https://issues.jenkins-ci.org/browse/JENKINS-62641.