You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nascif Abousalh-Neto (JIRA)" <ji...@apache.org> on 2008/01/19 01:52:34 UTC

[jira] Commented: (IVY-708) Circular Dependency messages in a resolve do not reflect the configuration used during the resolve

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

Nascif Abousalh-Neto commented on IVY-708:
------------------------------------------

Just want to add that this is more serious then just the warnings: It prevents us from changing the circularDependencyStrategy to "error" to fail the builds as soon as a user introduces a circular dependency (and they will...) in the "compile" configuration. Right  now we can't due to the "false positives" generated by this problem. So pretty soon we might have real circular dependencies to deal with.

Also it would be nice if the ResolveEngine could be made configuration-aware in a generic way, as to also address a similar limitation in the buildlist task.
https://issues.apache.org/jira/browse/IVY-290. This task would be really helpful in the implementation of an Ivy-aware Continuous Integration process, to find the subgraph that needs to be rebuilt given a set of leaves - but we need to be able to specify for which configuration, otherwise we will have circular dependencies *and* unnecessary nodes added to the result.

> 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
>
> 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.