Hi there, We are evaluating Artifactory to be used as our local/remote repository. Our application uses a custom *cxf-2.6.6 jar*.
We've manually deployed the cxf jar into libs-release-local. But each time we do a local build, Artifactory downloads a version of cxf 2.6.6 from the remote maven repository into ext-release-local. 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. Both *libs-release-local & ext-release-local *are mapped to the same virtual repository *libs-release*, so this is strange. Even if I delete it 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)? But then isn't it a bug? Please advice. Regards Aneesh -- View this message in context: http://forums.jfrog.org/Artifactory-ignores-artifacts-in-libs-release-local-tp7578665.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
