[
https://issues.apache.org/jira/browse/IVY-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John McCarthy updated IVY-1174:
-------------------------------
Attachment: IVY-1174.zip
I've reproduced this issue with build #216 from Ivy's Hudson,
https://hudson.apache.org/hudson/view/Ant/job/Ivy/216/
The attached project tests for this issue matching the provided description.
Ivy is evicting module_parent 1.0.0 for revision 1.0.3 but is retaining the
configuration for 1.0.0 and attempting to apply it to 1.0.3, which appears
inappropriate.
> 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.
-
You can reply to this email to add a comment to the issue online.
