[ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636598#action_12636598 ]
Xavier Hanin commented on IVY-933: ---------------------------------- I think Ivy trust the dependency declaration, and not the pom information, so it behaves the same way as maven. And I think inconsistent groupId, artifactId and revision are supported. I may be wrong though, it's only from the top of my head. > Maven2 parser checks version in the POM with the expected version > ----------------------------------------------------------------- > > Key: IVY-933 > URL: https://issues.apache.org/jira/browse/IVY-933 > Project: Ivy > Issue Type: Bug > Components: Maven Compatibility > Affects Versions: 2.0-RC1 > Reporter: Maarten Coene > > When Ivy downloads a POM, it checks if the version inside the POM is the same > as the expected version. > Maven2 doesn't check this. > For instance: http://repo1.maven.org/maven2/jdo/jdo/2.0-beta/jdo-2.0-beta.pom > Ivy will fail resolving this dependency, maven2 doesn't fail. > Even more: maven2 will download the 2.0-beta jar, but inside the POM the > version is 1.0.1, so it seems that maven2 uses the version from the URL > instead of the version from the POM. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.