You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2008/10/02 22:15:44 UTC
[jira] Created: (IVY-933) Maven2 parser checks version in the POM
with the expected version
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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636939#action_12636939 ]
Maarten Coene commented on IVY-933:
-----------------------------------
I just did a test and it seems that Ivy is taking the version from the pom, not from the dependency declaration :-(
> 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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "James Poli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799776#action_12799776 ]
James Poli commented on IVY-933:
--------------------------------
Our team has noticed "bad revision" ERROR doesn't cause a build failure if the module is found later in the resolve. This to us is a hidden ERROR only found when we interrogated the build log. Could an attribute be added to configure this type of error to cause a build failure?
Thanks in advance, Jim
> 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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636756#action_12636756 ]
Maarten Coene commented on IVY-933:
-----------------------------------
ok, I'll check which version Ivy will take...
If it does trust the dependency declaration, I'll set the checkconsistency property to "false" by default on the ibiblio resolver as you suggested. Ok?
> 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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799907#action_12799907 ]
Maarten Coene commented on IVY-933:
-----------------------------------
Jim, could you give an example of this behaviour?
And are you sure that you specified checkconsistency="true" on your resolver?
Maarten
> 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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636540#action_12636540 ]
Xavier Hanin commented on IVY-933:
----------------------------------
Actually this behaviour is supported in Ivy, but it isn't the default : you just need to set checkconsistency="false" on the resolver. Maybe we should make checkconsistency false by default on ibiblio resolver?
> 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.
[jira] Commented: (IVY-933) Maven2 parser checks version in the POM
with the expected version
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ 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.