I don't like to use version ranges and I agree that it is evil. This is just example that it is possible.
I just want to use the latest version from full dependency tree. This is absolutely reproducable. Do you agree with that? Now I set version of A in D each time some middle artifact is changed. I have a great library tree and when some middle library starts to depend on new version of A I set also this version in D. Absolutely always in D I set the latest version from full dependency tree. Do you have the experience where this wasn't the case for your library trees? So, I want this to be done automatically.. If I need to know version of A that will be used, I can always do it by dependency:list or dependency:tree. What is the problem with that workflow? -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4673465.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
