ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sven Zethelius (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IVY-1339) LatestCompatibleConflictManager exception on conflict
Date Wed, 21 Mar 2012 21:18:37 GMT

     [ https://issues.apache.org/jira/browse/IVY-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sven Zethelius closed IVY-1339.
-------------------------------

    Resolution: Invalid

The problems I was running into was due to IVY-1340  With that fixed and correct ranges (some
of my previous comments mistakenly had incorrect ranges), it degrades back to IVY-1233, which
is still not fixed in trunk.
                
> LatestCompatibleConflictManager exception on conflict
> -----------------------------------------------------
>
>                 Key: IVY-1339
>                 URL: https://issues.apache.org/jira/browse/IVY-1339
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0
>         Environment: Windows 7, Ant 1.8.1, Ivy 2.2.1.alpha_20120313100444
>            Reporter: Sven Zethelius
>         Attachments: ivy.txt
>
>
> This is a followup bug to IVY-1233.  With IVY-1233 fixed in the trunk, the conflict manager
no longer infinite loops, but on an unresolved conflict, its not erroring, instead an exception
is occurred.
> Repro:
> A (being built) Depends on B pVer.main.+, C \[1.0,2.0\[, D \[1.5,1.7\[
> B pVer.main.0.0 Depends on D \[1.6.1,2.0\[
> B 1.0.0 Depends on D \[1.6.1,2.0\[
> B 1.1.0 Depends on D \[1.6.1,2.0\[
> C 1.0.0 Depends on B \[1.0,2.0\[, D \[1.6.0,1.7\[
> C 1.1.0 Depends on B \[1.1,2.0\[, D \[1.6.0,1.7\[
> D no Dependencies
> The dependency on B is not resolvable since A and C don't agree on revision ranges.
> Expected:
> Error stating the module(s) that could not be resolved.
> Actual:
> Exception complaining about unrelated module.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message