We have a local artifactory repository setup for caching. It is configured in our projects, but when I'm looking at stdout of the build process I see rows like this
Downloading: http://ourserver/artifactory/our-repo/javax/transaction/jta/1.1/jta-1.1-sources.jar
Downloading: http://repo1.maven.org/maven2/javax/transaction/jta/1.1/jta-1.1-sources.jar
Downloaded: http://repo1.maven.org/maven2/javax/transaction/jta/1.1/jta-1.1-sources.jar (25 KB at 54.5 KB/sec)
So it looks like it is trying to download the jar from the local repository AND from Maven Central and then actually uses Maven Central).
If I copy the url of the local repository in my browser I get the jar without a problem.
If I check with the admin application of artifactory I can see the artefact.
Can anybody explain why Maven Central is used at all?
UPDATE: What was going on and what I did:
orien's answer explaines why Maven Central was accessed at all.
mliebelt comments hinted me towards my solution: Looks like our local repository was to slow to answer when it had to download the artifact first. I configured the cache to eagerly download jars and sources when a pom gets requested. This should reduce the number of artifacts downloaded from elsewhere.
http://ourserver/artifactory/our-repo-cache/javax/...
. – mliebelt