Carlton, It depends on how you ivy:resolve this artifact. To pick up the 'latest.integration' artifact it needs to be published with revision set to 'latest.integration' first, and when you ivy:resolve it you need to set resolveMode="dynamic".
Aleksey > Subject: revConstraint doesn't constrain with latest.integration > Date: Fri, 10 Jul 2009 08:54:42 -0400 > From: [email protected] > To: [email protected] > > 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. > ==================================================== _________________________________________________________________ Windows Live™ SkyDrive™: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009
