title: Artifactory ignores artifacts deployed into libs-release-local
body: <p>We are evaluating Artifactory to be used as our local/remote repository. Our application uses a custom <strong>cxf-2.6.6 jar.</strong>  We've manually deployed the cxf jar into <strong>libs-release-local</strong>. But each time we do a local build, Artifactory downloads  a version of cxf 2.6.6 from the remote maven repository into <strong>ext-release-local</strong>. As a result there will be two copies of cxf 2.6.6.jar and unfortunately our local build uses only the downloaded cxf instead of the one we deployed. </p>
  
  <p>Both <strong>libs-release-local</strong> &amp; <strong>ext-release-local</strong> are mapped to the same virtual repository <strong>libs-release</strong>, so this is strange. Even if I delete the cxf from ext-release-local it downloads again. How do I restrict this? I could probably deploy the cxf into ext-release-local (I haven't tried)? </p>
  
  <p>But then isn't it a bug? Please advice. </p>