SlinnHawkins, Jon (ELS-CAM) wrote:
Hi,
Is there any way of forcing a dependency to use the highest version available ?
Ranges is the right way to do it.
For example :
Does "[4.0,)" grab the highest version above 4.0, or does it still use a “best
fit” with the other dependencies in the tree
Current resolver will, by default, use nearest/newest approach - if
there is 4.1 on level 2 and 4.4 on level 3, it will go for 4.1. If they
are both on the same level (distance from the dependency tree root), it
will grab the newest.
Please be aware that there might be issues in resolving ranges spanning
more'n two levels. We are working on fixing all that in the new resolver.
Thanks,
Oleg
I’ve tried it and it appears to go for the highest version, I just want to be
sure.
Also, The version ranges do not seem to work in the dependencyManagement
section – is this intentional ?
Thanks in advance
Jon
This email is from Elsevier Limited, a company registered in England and Wales
with company number 1982084,
whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford,
OX5 1GB, United Kingdom.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
