You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Carl Myers (JIRA)" <ji...@apache.org> on 2010/09/17 22:57:32 UTC
[jira] Created: (IVY-1228) latest-compatible dependency manager
seems broken (acts like strict dep manager)
latest-compatible dependency manager seems broken (acts like strict dep manager)
--------------------------------------------------------------------------------
Key: IVY-1228
URL: https://issues.apache.org/jira/browse/IVY-1228
Project: Ivy
Issue Type: Bug
Affects Versions: 2.2.0-RC1, 2.1.0
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;3.1.1.0.326356 (needed by []) conflicts with myorg#mydeps;3.1.1.0.325888 (needed by [myorg#myclient;3.1.1.0.999325879, myorg#myshared;3.1.1.0.999325879])
{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;3.1.1.0.326356 blacklisted to evict myorg#mydeps;3.1.1.0.326356 in favor of myorg#mydeps;3.1.1.0.325888 in myorg#myserver;working@cmyers.example.com 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.
[jira] Commented: (IVY-1228) latest-compatible dependency manager
seems broken (acts like strict dep manager)
Posted by "Carl Myers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910782#action_12910782 ]
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: https://issues.apache.org/jira/browse/IVY-1228
> 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;3.1.1.0.326356 (needed by []) conflicts with myorg#mydeps;3.1.1.0.325888 (needed by [myorg#myclient;3.1.1.0.999325879, myorg#myshared;3.1.1.0.999325879])
> {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;3.1.1.0.326356 blacklisted to evict myorg#mydeps;3.1.1.0.326356 in favor of myorg#mydeps;3.1.1.0.325888 in myorg#myserver;working@cmyers.example.com 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.
[jira] Updated: (IVY-1228) latest-compatible dependency manager
seems broken (acts like strict dep manager)
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-1228:
-------------------------------
Fix Version/s: (was: 2.2.0)
Component/s: Core
Sorry Carl, this won't make it in the 2.2.0 release which is about to be released very shortly now...
Maybe it could get into the 2.2.1 release if you are able to send us a patch or a reproducible testcase.
thanks,
Maarten
> latest-compatible dependency manager seems broken (acts like strict dep manager)
> --------------------------------------------------------------------------------
>
> Key: IVY-1228
> URL: https://issues.apache.org/jira/browse/IVY-1228
> Project: Ivy
> Issue Type: Bug
> Components: Core
> 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
>
> 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;3.1.1.0.326356 (needed by []) conflicts with myorg#mydeps;3.1.1.0.325888 (needed by [myorg#myclient;3.1.1.0.999325879, myorg#myshared;3.1.1.0.999325879])
> {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;3.1.1.0.326356 blacklisted to evict myorg#mydeps;3.1.1.0.326356 in favor of myorg#mydeps;3.1.1.0.325888 in myorg#myserver;working@cmyers.example.com 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.
[jira] Commented: (IVY-1228) latest-compatible dependency manager
seems broken (acts like strict dep manager)
Posted by "Carl Myers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910861#action_12910861 ]
Carl Myers commented on IVY-1228:
---------------------------------
If I can build my own ivy jar with my patch for now, that would unblock me, so I will see about magicking up the patch. Then everyone wins.
Failing that, I will definitely post a more complete repro case, which I would need to formulate said patch anyways.
Thanks!
-Carl
> latest-compatible dependency manager seems broken (acts like strict dep manager)
> --------------------------------------------------------------------------------
>
> Key: IVY-1228
> URL: https://issues.apache.org/jira/browse/IVY-1228
> Project: Ivy
> Issue Type: Bug
> Components: Core
> 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
>
> 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;3.1.1.0.326356 (needed by []) conflicts with myorg#mydeps;3.1.1.0.325888 (needed by [myorg#myclient;3.1.1.0.999325879, myorg#myshared;3.1.1.0.999325879])
> {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;3.1.1.0.326356 blacklisted to evict myorg#mydeps;3.1.1.0.326356 in favor of myorg#mydeps;3.1.1.0.325888 in myorg#myserver;working@cmyers.example.com 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.