I guess the best thing to do is to raise an issue in http://jira.codehaus.org/browse/MEV as described there : http://maven.apache.org/guides/mini/guide-maven-evangelism.html . The thing you describe are clearly errors in the repository.
As a workaround, you can may try to use an other repository where you can install the correct poms (or ivy.xml files). Maybe using a dual resolver. Note also that ivy can work with a repository without pom.xml nor ivy.xml when the modules have no dependencies. I hope it helps. Gilles 2007/5/25, nirvdrum <[EMAIL PROTECTED]>:
Hi, As noted earlier, I'm looking to move from maven2 over to ant+ivy. During the migration, I've run across problems with a few POMs on ibiblio. maven2 apparently deals with the problems okay, since I never had problems downloading the files. ivy doesn't seem to allow me to. Is there anyway to tell ivy to download the files no matter what? As an example of the problems, one POM marks a version as 4.0.1, while the artifact is actually at version 4.0.2. ivy finds the files in the correct path, but then compares against the POM and borks when the versions don't match. In another, the organization defined in the POM does not match that used as the path to the artifact. Once again, ivy finds the file fine, but borks when doing a consistency check on the POM. Any help would be much appreciated. Thanks, Kevin -- View this message in context: http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248 Sent from the ivy-user mailing list archive at Nabble.com.
-- Gilles SCOKART
