[ 
https://issues.apache.org/jira/browse/IVY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025695#comment-16025695
 ] 

ASF GitHub Bot commented on IVY-1540:
-------------------------------------

GitHub user jaikiran reopened a pull request:

    https://github.com/apache/ant-ivy/pull/27

    Fix IVY-1540

    The commit here fixes the issue reported in 
https://issues.apache.org/jira/browse/IVY-1540. The dependency tree task now 
takes into account any potential circular dependencies that could result into a 
indefinite recursive calls.
    
    This also includes a test case to verify such a use case.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jaikiran/ant-ivy ivy-1540

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ant-ivy/pull/27.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #27
    
----
commit 6cb32bd33e0e1d1758a3ed1d50df03b65032d9ac
Author: Jaikiran Pai <jaikiran....@gmail.com>
Date:   2017-05-23T08:15:39Z

    IVY-1540 Fix infinite loop in dependencytree, caused to due circular 
dependencies (coming in via Maven module descriptors)

----


> Infinite loop in dependencytree
> -------------------------------
>
>                 Key: IVY-1540
>                 URL: https://issues.apache.org/jira/browse/IVY-1540
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.4.0
>            Reporter: Brett Wooldridge
>
> A 3rd party library with circular dependencies causes an infinite loop 
> displaying the dependency tree.  The code needs to use a hashmap or hashset 
> to track what has been displayed in a given tree branch and bail when it 
> encounters a node previously occurring in the branch.
> This dependency is circular, and can be used for testing:
> org.apache.xmlgraphics#batik-bridge;1.7



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to