title: Maven build on Jenkins - upstream version range resolves to version being built in a concurrent job
body: <p>We have a Jenkins build which in it's initial stage tries to determine the latest deployed version of some dependencies via version ranges, which are also built by that same Jenkins instance. Each build is for several artifacts, all with a shared version, so we want to select the latest version which has been completed. We do this by using a special pom which has dependencies on specific poms - these are deployed last by the other builds.</p>
  <p>The issue is that if one of the other builds is running, but has not yet deployed the pom, maven's version range resolution winds up selecting the version for the build in progress and then fails as some of the dependencies haven't been built yet.</p>
  <p>This isn't a downstream build kicked off by the dependency. In any case, we've tried the &quot;Enable isolated resolution for downstream builds&quot; and &quot;Resolve artifacts from Artifactory&quot; but neither have helped.</p>