Re: maven-metadata-central.xml is missing versions in local repo
Markku Saarela wrote: > > This can be caused by Artifactory if checksums does not match and you > Artifactory is configured to fail if checksums doesn't match. > > Markku > Hi, thank you for the suggestion, but our artifactory is configured to "ignore and return generated checksums". Florian -- View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28337643.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
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 -- View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28326625.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Hi, Wayne Fay wrote: > > What does your pom file dependency to log4j look like? > > Wayne > > This is the dependency: struts struts Today's nightly build another project failed with [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [1.2.6,1.2.6] org.codehaus.xfire:xfire-all:jar:null from the specified remote repositories: central (http://maven.uniqa.at/artifacts/repo), snapshots (http://maven.uniqa.at/artifacts/repo) with this dependency in the pom.xml org.codehaus.xfire xfire-all [1.2.6] Deleting the xfire folder from the local repo and running the build again resolved the problem (and generated a correct metadata xml file). Florian -- View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28325521.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-metadata-central.xml is missing versions in local repo
Hi, I have a multi module build using maven 2.2.1 and artifactory 2.2.0. The first submodule requests log4j 1.2.9 resulting in the files [1] downloaded correctly. The second submodule request log4j 1.2.14 resulting in some files added [2] As you can see maven now creates a maven-metadata-central.xml [3] which only contains log4j 1.2.15+16. The build fails with: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.9,1.2.9] log4j:log4j:jar:null But Version 1.2.9 is present in the file system! I wipe out the local repo before the nightly build, this problem only apperas every two or three weeks and at the moment I cannot say why. But at the moment I have a VMWare Snapshot where I can reproduce it. It also appereas also at some other artifacts, especially struts and cobertura-maven-plugin. * [1] * D:\mavenrepo\log4j\log4j>dir /s Datenträger in Laufwerk D: ist HUDSONDATA2 Datenträgernummer: F020-662E Verzeichnis von D:\mavenrepo\log4j\log4j 21.04.2010 12:15 . 21.04.2010 12:15 .. 21.04.2010 12:16 1.2.9 0 Datei(en) 0 Bytes Verzeichnis von D:\mavenrepo\log4j\log4j\1.2.9 21.04.2010 12:16 . 21.04.2010 12:16 .. 21.04.2010 12:16 352.291 log4j-1.2.9.jar 21.04.2010 12:16 40 log4j-1.2.9.jar.sha1 21.04.2010 12:16 40 log4j-1.2.9.jar.tmp.sha1.tmp 21.04.2010 12:15 144 log4j-1.2.9.pom 21.04.2010 12:15 40 log4j-1.2.9.pom.sha1 21.04.2010 12:15 40 log4j-1.2.9.pom.tmp.sha1.tmp 6 Datei(en)352.595 Bytes * [2] * D:\mavenrepo\log4j\log4j>dir /s Datenträger in Laufwerk D: ist HUDSONDATA2 Datenträgernummer: F020-662E Verzeichnis von D:\mavenrepo\log4j\log4j 21.04.2010 12:18 . 21.04.2010 12:18 .. 21.04.2010 12:18 1.2.14 21.04.2010 12:18 1.2.9 21.04.2010 12:18 352 maven-metadata-central.xml 21.04.2010 12:18 40 maven-metadata-central.xml.sha1 2 Datei(en)392 Bytes Verzeichnis von D:\mavenrepo\log4j\log4j\1.2.14 21.04.2010 12:18 . 21.04.2010 12:18 .. 21.04.2010 12:182.374 log4j-1.2.14.pom 21.04.2010 12:18 40 log4j-1.2.14.pom.sha1 2 Datei(en) 2.414 Bytes Verzeichnis von D:\mavenrepo\log4j\log4j\1.2.9 21.04.2010 12:18 . 21.04.2010 12:18 .. 21.04.2010 12:16 352.291 log4j-1.2.9.jar 21.04.2010 12:16 40 log4j-1.2.9.jar.sha1 21.04.2010 12:15 144 log4j-1.2.9.pom 21.04.2010 12:15 40 log4j-1.2.9.pom.sha1 4 Datei(en)352.515 Bytes * [3] * log4j log4j 1.2.15 1.2.16 1.2.15 1.2.16 20100331042604 I am not sure which points to investigate next, it's such a strange bug. Best Regards Florian -- View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28288000.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
