ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-933) Maven2 parser checks version in the POM with the expected version
Date Fri, 03 Oct 2008 06:38:44 GMT

    [ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636551#action_12636551
] 

Maarten Coene commented on IVY-933:
-----------------------------------

I don't think that will be enough, if the version is different, maven2 will use the version
definied in the filename, not in the POM. I think Ivy will always use the version from the
POM? 

And maybe we should see what maven does when groupId and artifactId is also inconsistent in
this case?

> 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.


Mime
View raw message