This can be caused by Artifactory if checksums does not match and you
Artifactory is configured to fail if checksums doesn't match.
Markku
On 22.4.2010 12:53, Florian R. wrote:
Wayne Fay wrote:
What MRM are you running -- Nexus, Artifactory, Archiva, etc? Are you
sure this is a problem in Maven and not something related to your MRM?
We are running Artifactory 2.2.0.
Maven downloads the files (no HTTP 404s or something like that) and can't
find it afterwards. IMHO this is related to maven.
We partially solved the problem now, it seems the log4j problem was releated
to a parent pom containing a fixed version and that was confusing maven. But
the problem is not reproducable with a simplyfied project using exact this
constellation :(
Does anyone know which fact forces maven to create the
maven-metadata-central.xml to get some idea why this happens?
Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
