[ https://issues.apache.org/jira/browse/IVY-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin updated IVY-1022:
------------------------------
Issue Type: Improvement (was: Bug)
I don't classify this as a bug, because if you use a forced resolver in your source resolver
chain, it's not that much a bug what happen. It's more a settings problem IMHO. But having
an easy way to prevent forced resolvers from being forced during install could be an interesting
improvement.
> Forced resolver behavior is inappropriate for ivy:install
> ---------------------------------------------------------
>
> Key: IVY-1022
> URL: https://issues.apache.org/jira/browse/IVY-1022
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 2.0
> Reporter: Carlton Brown
>
> I tried to install a certain revision of a module from a chained resolver to an fs resolver,
and observed that Ivy installed a revision other than what I specified. After investigation
I noticed that the chain contained a forced fs resolver. I removed the forced resolver from
the chain, replacing it with an equivalent un-forced fs resolver. The install worked correctly
after that.
> I think that ivy:install should not be doing any dynamic version resolution at all.
It should in every case use the literal module identifiers that are passed to it. This
being the case, install should ignore a force attribute wherever it is encountered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.