ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Myers (JIRA)" <>
Subject [jira] Commented: (IVY-1228) latest-compatible dependency manager seems broken (acts like strict dep manager)
Date Fri, 17 Sep 2010 20:57:36 GMT


Carl Myers commented on IVY-1228:

Note:  Looks like it *might* be related to IVY-1204, but I don't think so.

> latest-compatible dependency manager seems broken (acts like strict dep manager)
> --------------------------------------------------------------------------------
>                 Key: IVY-1228
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.1.0, 2.2.0-RC1
>         Environment: I believe all environments are affected, but I am testing in a Linux
2.6 Environment using a 1.5 JDK and Ant 1.7.1
>            Reporter: Carl Myers
>            Priority: Critical
>             Fix For: 2.2.0
> It appears the "latest-compatible" conflict manager is acting like the strict conflict
manager in the following case.
> The actual error I get is:
> {noformat}
> impossible to resolve dependencies:
>         myorg#mydeps; (needed by []) conflicts with myorg#mydeps;
(needed by [myorg#myclient;, myorg#myshared;])
> {noformat}
> How is this error even possible if "latest compatible" is in use?  Surely, the version
ending in "325888" is the latest compatible, 326356 is later but not compatible.
> Looking at the log, I see:
> {noformat}
> DEPRECATED: using conflicts section is deprecated: please use hints section instead.
Ivy file URL: ...
> {noformat}
> Is this why it isn't working?  Did backcompat get broken and I need to change my ivy.xml?
> I also see:
> {noformat}
> BLACKLISTING [myorg#mydeps; blacklisted to evict myorg#mydeps;
in favor of myorg#mydeps; in myorg#myserver; for default]
> {noformat}
> It looks like 326356 is blacklisted in favor of the newer version, but some package is
not compatible with that newer version so it ought to use the older one instead.
> I tested and confirmed this problem with Ivy 2.2.0-rc1 (20100629224905), and also Ivy
2.1.0 (20090925235825).  I confirmed this problem is NOT present in 2.0.0 (20090108225011).
> Because my continuous build environment is constantly building and publishing new versions,
a local build is impossible unless "latest-compatible" works.  The fact that it works with
older ivy is kinda suggestive it is a bug (or changed behavior), though I am glad to try any
suggestions you folks might have.
> I will be pulling the code and investigating myself if I can find time.
> Thanks!

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message