We are using Artifactory 2.4.2 and have been observing issues with remote repos and maven unique snapshots (timestamp versioned snapshots). We publish the unique snapshots to local repo in Artifactory and one of our remote repo in Artifactory is pointing to an old instance of Artifactory.
The problem is that unique snapshot cached in remote repo doesn't get refreshed and Artifactory continues reading artifacts from remote repo even though local repo has new snapshots in it. I am not sure if it has got something to do with Layout repository? i have chosen maven-2-default as the layout for the remote repo. Btw, i don't see maven-3-default layout and i can't create new layouts as well? Further, I know that local repos have higher precedence, followed by remote repo cache and then remote repo itself. However, i would like to understand how does caching work in Artifactory with the below mentioned retrieval scenario. Let's assume we have two remote repos (A & B). A is at higher precedence than B. B has cached an artifact "foo" in its cache. Now if i look for an artifact "foo", will Artifactory try to search "foo" in A before finding it in B or will it directly give the artifact from B? Can someone help? Thanks -- View this message in context: http://forums.jfrog.org/Remote-repo-unique-snapshots-refresh-issue-tp7578883.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
