We’re struggling with the following issue.
We set up a proxied Nexus pro repository infrastructure. We have a Nexus Master repository and two Nexus Slave repositories. We use proxy functionality, moreover the smart proxy functionality.
We have a multiproject build environment and make use of ivy dependencies with gradle. If nothing goes wrong, the published artifacts are proxied actively (smart proxy can take care of this) to the slaves and can be resolved also using dynamic versions (e.g. ‘1.1.+’). If a network connection is broken or even accessing older releases from the master, that have been published when the slaves where not available, then the resolving of an artifact at the slave doesn’t work as expected.
Expectation would be, that nexus resolves to the most current version on the master and fetches it to the slave. This doesn’t work. We set up a test scenario, where the slave has older versions than the master. Resolving ivy dependencies on the slave never resolves them on the master.
Gradle Documentation says, that ivy and dynamic versions are resolved using directory listings. This obviously isn’t possible on proxy instances.
Has anyone any idea how to cope with that issue?