malliaridis commented on PR #4098: URL: https://github.com/apache/solr/pull/4098#issuecomment-3861028005
> I went into our toml and replaced , version.ref = "google-cloud-core" with `` (nothing), as a quick experiment, and I see it worked. This means we can do this for all other dependencies that are included in a BOM to do similarly. How does the dependency resolution behave in this case when you have not added to a specific module the BOM as platform dependency, and included that dependency that has no version? I remember a situation where it was unable to resolve dependencies without versions under certain circumstances. I also saw that adding the BOM to the module explicitly dependency drift is resolved. Would that be the way to go here? > I don't understand why we need to maintain the individual dependency versions when com.google.cloud:google-cloud-bom already contain their versions? Should be ebough for us to bump the bom? Is it the cutterslade plugin that enforces this verbosity? Note that the platform module is currently not able to properly include BOMs and their constraints. This is probably why. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
