[
https://issues.apache.org/jira/browse/IVY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-861.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0-RC1
I've added a unit test to reproduce this, and fixed the problem. Actually the
bug was bigger than that and related to IVY-681 changes. Things should be more
stable now, but I still suspect we may ran into issues in complex conflict
resolution with dynamic revisions.
> dynamic revision resolve does not throw error when configuration is missing
> ---------------------------------------------------------------------------
>
> Key: IVY-861
> URL: https://issues.apache.org/jira/browse/IVY-861
> Project: Ivy
> Issue Type: Bug
> Reporter: Shawn Castrianni
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
>
> Let's assume A depends on latest B with configuration B1. I publish B with
> configuration B2. I then run resolve for A and it properly finds the latest
> revision of B but does NOT download any artifacts. It doesn't even complain
> that configuration B1 is missing. If I run -verbose I can see this message:
> [ivy:resolve] configuration required by evicted revision is not available in
> selected revision. skipping B1 in Landmark#B#HEAD;LOCAL
> 1. I think this message should be shown without having to use -verbose
> 2. An error should be thrown since the selected revision does not have the
> configuration requred by the dependency
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
