Hi Mads The only way I've found to force that behavior is to declare my dependency rev="latest.integration" and of course, ensure that the status="integration" for each of the modules you publish. This assumes you've set latest="latest-time" in your resolvers, of course.
HTH, Jim "Tandrup, Mads" <[email protected]> writes: > Hello > > We have mayby a bit special situation where we have two repositories that > both contains the same modules with the same version numbers. They are > however build at different times. And we would like to receive the module > with the latest publication time. > But as far as I can see when the chain resolver resolves a specific version, > it always returns the first module with that revision? Is there any way to > make the chain resolver go through all the sub resolves and select the module > with the latest modifcation time? > > Best regards, > Mads > > Capgemini is a trading name used by the Capgemini Group of companies which > includes Capgemini Danmark A/S, a company registered in Denmark (number > 25606965) whose registered office is at ?rnegaardsvej 16 - 2820 Gentofte. > > > > > > > This message contains information that may be privileged or confidential and > is the property of the Capgemini Group. It is > intended only for the person to whom it is addressed. If you are not the > intended recipient, you are not authorized to > read, print, retain, copy, disseminate, distribute, or use this message or > any part thereof. If you receive this message > in error, please notify the sender immediately and delete all copies of this > message.
