Hi Aneesh, I'm a bit confused, artifacts downloaded from maven central won't be stored in ext-release-loacal as this is a local repository. Artifacts downloaded from remote repositories are stored in the remote-repo's cache, for example: artifacts resolved from repo1 will be stored in repo1-cache. You can look at your virtual repository's configuration to see the repository order in which Artifactory looks for artifacts. Regardless of the repositories order, Artifactory will always look in local repositories first, then in remote caches and finally in remote repositories, We did have a bug regarding this issue, but it was resolved. You can see it here <https://issues.jfrog.org/jira/browse/RTFACT-5100> . So make sure you are using Artifactory 2.6.5 or above. Then, if you still didn't find the artifact's source, you could use the REST API trace query, you can read more about it here <http://wiki.jfrog.org/confluence/display/RTF/Artifactory's+REST+API#Artifactory'sRESTAPI-TraceArtifactRetrieval> . What Mirko said is true, indeed it's bad practice and could be misleading.
Hope this helps, Itamar -- View this message in context: http://forums.jfrog.org/Artifactory-ignores-artifacts-in-libs-release-local-tp7578665p7578693.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
