gnodet commented on issue #11391: URL: https://github.com/apache/maven/issues/11391#issuecomment-3531450417
@vlsi I'm thinking that we just need a new strategy in the resolver. We recently introduced `highest` in the resolver, but that one does not take direct dependencies into account, following the unwritten rule that Maven does not override what the user explicitly stated. If we relax this rule, assuming the user means "I require at least this version of the lib", we can add a new `flexible` (or whatever the name will be) strategy that will select the highest version for transitive _and_ direct dependencies. Compared to my original proposal, it's much simpler, but does not allow to tune a given dependency explicitly. The question is whether the added complexity (to configure for a given strategy) actually solves a real use case or not. -- 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]
