[
https://issues.apache.org/jira/browse/IVY-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060737#comment-13060737
]
Pit Waldispühl commented on IVY-1174:
-------------------------------------
To further clarify the issue: It's ok that Ivy insists on the configuration of
the evicted version e. g. in case where the dependency of ModA, rev 1.0.0 was
mapped to a specific configuration like 'mysql'. In this case, eviction should
not lead to e. g. rev 2.0.0 of ModA with a configuration like 'postgres' since
a dependency on 'mysql' was the initial intention.
But in the case of the 'default' configuration, which is implicitly constructed
by ivy when no configuration was defined, ivy should not insist on 'default'
when ModA, rev 1.0.0 gets evicted and replaced with ModA, rev 2.0.0 if this new
revision has an explicit mapping to a configuration other than 'default'; The
dependency on 'default' with ModA, rev 1.0.0 was not an intention (but an
internal construction of ivy you shouldn't have to care for in such cases).
> 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
> Attachments: IVY-1174.zip
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
