You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Sven Zethelius (Created) (JIRA)" <ji...@apache.org> on 2012/03/20 21:43:47 UTC
[jira] [Created] (IVY-1339) LatestCompatibleConflictManager
exception on conflict
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
[jira] [Commented] (IVY-1339) LatestCompatibleConflictManager
exception on conflict
Posted by "Sven Zethelius (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234990#comment-13234990 ]
Sven Zethelius commented on IVY-1339:
-------------------------------------
Typo in my last comment:
LatestCompatibleConflictManager is choosing B pVer version, even though it doesn't fit into A's range.
A is specifying version [1.0,2.0[ of B, which pVer would not compare.
> 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
[jira] [Commented] (IVY-1339) LatestCompatibleConflictManager
exception on conflict
Posted by "Sven Zethelius (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233726#comment-13233726 ]
Sven Zethelius commented on IVY-1339:
-------------------------------------
Relevant ivy settings file part:
<latest-strategies>
<latest-revision name="expedia-latest-revision" />
</latest-strategies>
<conflict-managers>
<compatible-cm name="expedia-conflict-manager" latest="expedia-latest-revision"/>
</conflict-managers>
<version-matchers usedefault="false">
<vm-latest />
<vm-sub-version />
<vm-version-range />
</version-matchers>
<settings defaultResolver="${ivy.resolver}"
defaultLatestStrategy="expedia-latest-revision"
defaultConflictManager="expedia-conflict-manager"
/>
> 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
[jira] [Commented] (IVY-1339) LatestCompatibleConflictManager
exception on conflict
Posted by "Sven Zethelius (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234988#comment-13234988 ]
Sven Zethelius commented on IVY-1339:
-------------------------------------
It appears the exception is related to [https://issues.apache.org/jira/browse/IVY-1340]. When I fixed the NPE by changing file: to file://, the LatestCompatibleConflictManager now isn't realizing that it has incompatible ranges to resolve. It chooses the B pVer version, even though it doesn't fit into C's range.
> 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
[jira] [Closed] (IVY-1339) LatestCompatibleConflictManager
exception on conflict
Posted by "Sven Zethelius (Closed) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (IVY-1339) LatestCompatibleConflictManager
exception on conflict
Posted by "Sven Zethelius (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Zethelius updated IVY-1339:
--------------------------------
Attachment: ivy.txt
Resolve output
> 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