You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "jaikiran pai (Jira)" <ji...@apache.org> on 2019/09/23 17:11:00 UTC
[jira] [Comment Edited] (IVY-1587) Wrong POM translation for
dependencies appearing more than once
[ https://issues.apache.org/jira/browse/IVY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936043#comment-16936043 ]
jaikiran pai edited comment on IVY-1587 at 9/23/19 5:10 PM:
------------------------------------------------------------
Can you try this with our latest nightly build [https://builds.apache.org/view/All/job/Ivy/lastSuccessfulBuild/artifact/build/.|https://builds.apache.org/view/All/job/Ivy/lastSuccessfulBuild/artifact/build/] We fixed this recently as part of IVY-1580
When you try, do make sure to use a clean/fresh Ivy cache directory.
was (Author: jaikiran):
Can you try this with our latest nightly build [https://builds.apache.org/view/All/job/Ivy/lastSuccessfulBuild/artifact/build/.|https://builds.apache.org/view/All/job/Ivy/lastSuccessfulBuild/artifact/build/] We fixed this recently as part of IVY-1580
> Wrong POM translation for dependencies appearing more than once
> ---------------------------------------------------------------
>
> Key: IVY-1587
> URL: https://issues.apache.org/jira/browse/IVY-1587
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.5.0-rc1
> Reporter: Cédric Damioli
> Priority: Major
>
> Using
>
> {code:java}
> java -jar ivy.jar -dependency "org.slf4j" "slf4j-log4j12" "1.7.25" -confs default -types jar
> {code}
> With Ivy 2.4.0, I get two artifacts : slf4j-api.jar and slf4j-log4j12.jar
> With Ivy 2.5.0RC1, I only get {color:#333333}slf4j-log4j12.jar with no means to get the -api artifact {color}
>
> This seems to be related to the resolution of IVY-1576
>
> In the POM, the slf4j-api dependency is present twice, once for compile, once for tests.
> Before IVY-1576, it resulted in two different dependencies.
> With IVY-1576, there's only one dependency, offering only the test artifact.
>
> The fix was good for "merging" dependencies with classifiers, but in this case, the merge should not have occured
>
> I don't set this ticket as critical as there are workarounds, but it is at least very annoying
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)