You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2010/06/10 22:01:12 UTC

[jira] Updated: (IVY-1174) resolved module can include configurations of evicted versions

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

Maarten Coene updated IVY-1174:
-------------------------------

    Fix Version/s:     (was: 2.2.0-RC1)

I cannot reproduce the problem.
Could you provide an example ivy.xml for both your module_parent, module_middle, module_between and module_entry?


> resolved module can include configurations of evicted versions
> --------------------------------------------------------------
>
>                 Key: IVY-1174
>                 URL: https://issues.apache.org/jira/browse/IVY-1174
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0-RC2
>            Reporter: Willem Verstraeten
>
> Scenario:
> module_parent, with two revisions:
>   1.0, which has configurations default and runtime, where default extends runtime
>   1.0.3, which only has configuration default
> module_middle, which depends on module_parent:1.0
> module_between, which depends on module_parent:1.0.3
> module_entry, which depends on module_middle and module_between
> When resolving module_entry, version 1.0 of module_parent will be evicted, but ivy will complain about module_parent not having a runtime configuration. Apparently, ivy has mashed the configurations from the 1.0 version (which was evicted) with those of 1.0.3, where there actually is no runtime configuration.

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