melix,
@melix@mastodon.xyz avatar

At the risk of repeating myself, Maven's "closest" resolution strategy sucks a million. Sorry but I'm literally spending hours trying to figure out why a version declares in an imported BOM doesn't take precedence. And it's a fairly complex project with hundreds of deps, each overriding each others' dependency management blocks, because yeah sure that's the only way you can make that thing use the version you want, right? Let me cry.

melix,
@melix@mastodon.xyz avatar

seriously, how am I supposed to figure out WHO THE HELL wins over the 2.17.0 version I define in my BOM? My eyes are bleeding reading walls of dependency versions.

tbroyer,
@tbroyer@piaille.fr avatar

@melix Did you try mvn help:effective-pom -Dverbose?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • modclub
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • cubers
  • GTA5RPClips
  • thenastyranch
  • Youngstown
  • rosin
  • slotface
  • tacticalgear
  • ethstaker
  • kavyap
  • Durango
  • anitta
  • everett
  • Leos
  • provamag3
  • mdbf
  • ngwrru68w68
  • cisconetworking
  • tester
  • osvaldo12
  • megavids
  • khanakhh
  • normalnudes
  • JUstTest
  • lostlight
  • All magazines