Tim te Beek

Thanks for the start here @ThomasVitale ! I'm going to ask if @shanman190 has some guiding hints here for whether we want to make these changes as part of this...

hi! Thanks for the report; wasn't aware of any specific issues, but the combination of 9.1.0 + Java 25 is quite new, also to us. Like you we haven't seen...

I'll see if I can fit in running that reproducer when I get home Friday; any details you can already share here would be helpful.

Thanks for the added details! Indeed think that the problem here is that our parser for Kotlin, used by our Gradle parser, uses 1.9.x still, whereas that's not supported on...

This PR has been updated to also - fix #6322. **Additional changes for #6322:** - Handle BOM imports directly from the tag rather than through `findManagedDependency()` - This prevents incorrect...

Reverted to the earlier more minimal change here to make it easier to get this small fix in already.

Hi @elmuerte ; Thanks for the report! Such dynamic version numbers have historically been overlooked a bit indeed. Sounds like you're running into another edge case. From your stacktrace it...

Perhaps a good question to ask such that we're not running down the wrong path: should these dependencies be downloaded at all, or are they all from the same multi...

That helps confirm my suspicion indeed; we'd need to look at why we're even attempting to download that POM rather than getting it from the Maven execution context. Any help...

Thanks for diving in, tracing this all the way through and sharing your detailed notes here. Seems reasonable to make that adjustment here. We can look at any fall out...