Hi all, It appears to me that revision constraint is not respected when a forced resolver is encountered.
Given a dependency on a module "widget" defined as follows: <dependency org="com.company" name="widget" rev="latest.integration" revConstraint="3.0.+" changing="true" conf="default->site"/> If my fs repository contains versions 3.0.19.1 and 3.1-SNAPSHOT, I expect the 3.0.19.1 to be resolved. But the observed behavior is that Ivy resolves 3.1-SNAPHOT. Why is this? I expected that the 3.0.+ revConstraint would exclude any revision beginning with 3.1. Thanks in advance, Carlton ==================================================== This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you. ====================================================
