Well this is fun. Adding a new dependency to clas...
# springl
Larry Garfield
08/01/2024, 3:30 PMWell this is fun. Adding a new dependency to class A, and making no use of it (the variable is unused), is causing a type error in class B. (Class A does call class B.) How is that even possible, if I’m doing nothing with the new dependency? There’s no variable name collisions, I checked.
a
ashmelev
08/01/2024, 3:54 PMCheck your transitive dependencies. I've seen this behaviour when two classes pull in transitives and the transitives have conflicting versions
l
Larry Garfield
08/01/2024, 4:01 PM… Actually never mind. I literally just got a layoff notice as I posted this, so it’s no longer my problem. 😕 Thanks though.
😧 6
a
ashmelev
08/01/2024, 4:03 PMOh, no.... sorry...good luck
s
Sam
08/01/2024, 4:11 PMWell this thread certainly took a turn! Sorry to hear that, Larry. I'm glad you don't have to worry about debugging the Spring problem any more, though! Silver linings, I guess.
l
Larry Garfield
08/01/2024, 4:11 PMYeah. I was considering if I should ask my manager about transferring to a different team, but this isn’t quite what I meant…
😄 1
😬 1
Larry Garfield
08/01/2024, 4:11 PMNo idea if whatever I do next will even involve Kotlin, so if not, so long and thanks for all the fish.
🍻 8