[
https://issues.apache.org/jira/browse/IVY-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913828#action_12913828
]
Archie Cobbs commented on IVY-1231:
-----------------------------------
Thank you, now I understand. Sorry for the noise.
But am I the only one who thinks this behavior is insane? :-)
In other words:
# Dependency #1 says "use anything later than 1.3.1".
# Dependency #2 says "use 2.1.17".
# So ivy's answer is... 5.0.4 ??
This to me makes absolutely no sense as the _default_ behavior of ivy. It
violates the
[POLA|http://en.wikipedia.org/wiki/Principle_of_least_astonishment] (principle
of least astonishment) in a big way.
First of all, where is the "conflict" ?... 2.1.7 is certainly greater than
1.3.1. But I see now ivy defines a conflict as any time there are two
dependencies on the same module. OK, whatever.
I guess all of this can be summed up as: latest-compatible should be the
default conflict manager for ivy, not latest-revision. And if that's not
possible, then there should be a way to change the default conflict manager
globally.. I don't see how so far from reading the docs, it just says "The
current default conflict manager is the 'latest-revision' conflict manager."
> Ivy reports a bogus unresolved dependency
> -----------------------------------------
>
> Key: IVY-1231
> URL: https://issues.apache.org/jira/browse/IVY-1231
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.0-RC1
> Environment: openSUSE 11.3, ant 1.7.1
> Reporter: Archie Cobbs
> Attachments: ivybug.zip
>
>
> Ivy is complaining about an unresolved dependency which does not exist:
> {noformat}
> [ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] :: UNRESOLVED DEPENDENCIES ::
> [ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] :: net.sourceforge.itext#itext;5.0.4:
> configuration not found in net.sourceforge.itext#itext;5.0.4: 'rtf'.
> It was required from
> org.jaspersoft#jasperreports;3.5.3 core
> [ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
> {noformat}
> There is no dependency on the "rtf" configuration in jasperreports 3.5.3
> (view it's ivy.xml file
> [here|http://ivyroundup.googlecode.com/svn/!svn/bc/1331/trunk/repo/modules/org.jaspersoft/jasperreports/3.5.3/ivy.xml]).
> In fact, there is no dependency on any "rtf" configuration by any module in
> the whole repository.
> To reproduce this bug:
> # Unpack the attached ZIP file to get IVYBUG directory
> # Copy {{ivy-2.2.0-rc1.jar}} into the IVYBUG directory
> # From within IVYBUG, run {{ant}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
