[JAVA-4201] AsynchronousTlsChannelGroup uses SLF4J directly Created: 17/Jun/21 Updated: 28/Oct/23 Resolved: 28/Jun/21 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.0 |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The vendored async tls code uses SLF4J directly and throws a NoClassDefFoundError. It should be updated to use the logging helper so it can fall back to the noop logger if SLF4J isn't available. Source: https://developer.mongodb.com/community/forums/t/mongo-java-driver-noclassdeffounderror/110941 |
| Comments |
| Comment by Githook User [ 25/Jun/21 ] |
|
Author: {'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}Message: Fixed Logging in vendored tlschannel (#735)
|