404 in metadata.xml
Issue Type: Bug
Affects Versions: 2.0.4
Environment: Standalone artifactory 2.0.4 behind apache 2.2.6 via mod_proxy
ProxyPass /artifactory http://acropolis:8081/artifactory
ProxyPassReverse /artifactory http://acropolis:8081/artifactory
Reporter: Justin Shapiro
Assignee: Yoav Landman
I keep getting 404 errors in my metadata.xml. The artifacts are being downloaded from the correct repo but instead of downloading the metadata.xml a 404 error is being stored saying it couldn't get what it needed from a different repo.
I have three virtual repos configured central, releases and snapshots
central is configured to handle snapshots and releases third-party only
releases is configure to only handle releases of our products
snapshots is configured to only handle snapshots of our products
the scenario is that the dependency gets downloaded from snapshots like /artifactory/snapshots/com/foo/bar/1.0/bar-1.0.pom
but the metadata is being fetched from /artifactory/central/com/foo/bar/metadata.xml it doesn't exist there so a 404 is returned. the 404 message is stored in the .m2 as metadata.xml resulting in broken builds
I am able to determin that the metadata is coming from the wrong repo because the stored html has the incorrect url in it. This happens to random artifacts so redeploying does not change the behavior. I am able to download the metadata by specifying the correct repo url.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.jfrog.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Get latest updates about Open Source Projects, Conferences and News.