:thinking_face: ...why in this world they did that...
# gradle
x
🤔 ...why in this world they did that?!
c
That's a long story, you can read a long discussion at the link below. But that long story short, G team likes the idea of BOM but disagrees with M team on some finer points of it. So Gradle 5's BOM feature is not really maven BOM support but rather a feature which is very similar to maven BOM. Here's the discussion: https://github.com/gradle/gradle/issues/4979
👌 1
That said, your problem might be caused by something different, this difference in implementation is just one possibility that came to my mind right away
x
I switched back and start using again the
dependencyManagement
block and the issue is gone, so I think that might be it...
👌 1
x
use
enforcedPlatform
instead of
platform
🤔 1
that said, if you’re using spring’s parent enforced platform won’t play nicely with kotlin 1.3
because it forces the versions to act like maven
except first one wins
x
Thanks for the tip...will give it a try.