Am 08/24/16 um 08:23 schrieb Hervé BOUTEMY: > version ranges: I hate version ranges... :) > notice: what is the issue with version ranges? the generated consumer pom can > contain version ranges, since it is a long-standing feature
It would be really cool if the whole dependency resolution could be done at build time and does not need to be performed when consuming an artifact again and again. Version ranges make this impossible. Currently we cannot change anything about dependency resolution between Maven versions. We cannot even fix resolution bugs and stay compatible. One way out of that would be to deploy the resolution result instead of the recipe to resolve the dependency tree. > notice: this is another good reason to finish Aether import first... :) +1 When separating the build and consumer pom we also need to support changing dependency resolution logic (enhance/fix/new feature) in a compatible way for that consumer pom. That's another issue we are running into frequently. Recent Maven version needs to provide the exact same dependency tree (including all bugs) of older versions and users need to manually opt-in to the fixes/new features/changes by some kind of consumer pom versioning. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
