Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1926564635.1219756064676.JavaMail.jira@brutus>
Date: Tue, 26 Aug 2008 06:07:44 -0700 (PDT)
From: "Xavier Hanin (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVY-708) Circular Dependency messages in a
 resolve do not reflect the configuration used during the resolve
In-Reply-To: <18090952.1200690513835.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xavier Hanin resolved IVY-708.
------------------------------

    Resolution: Fixed

I've fixed this bug by skipping the circular dependency handling done in sort when called after a resolve to order the resolved dependencies. Indeed in this case circular dependency checks are done during resolve, there is no reason to report them again (and as you pointed the information is not as precise as during resolve). This does not solve the buildlist problem, so I suggest you open a specific issue if you still have this requirement.

> Circular Dependency messages in a resolve do not reflect the configuration used during the resolve
> --------------------------------------------------------------------------------------------------
>
>                 Key: IVY-708
>                 URL: https://issues.apache.org/jira/browse/IVY-708
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-1
>         Environment: unix
>            Reporter: Jim Adams
>            Assignee: Xavier Hanin
>             Fix For: 2.0-RC1
>
>
> We have a dependency chain that has several configurations. We use compile and runtime configurations. We have no circular dependencies in the compile configuration but we do in the runtime configuration. During the resolve with the compile configuration we are getting circular dependency warnings which, when examined, follow the runtime configuration. It looks like the method CollectionOfModulesToSort.getModuleDesciptorDependency() does not look at the configuration.

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