ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-1022) Forced resolver behavior is inappropriate for ivy:install
Date Mon, 14 Jun 2010 22:11:14 GMT

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

Maarten Coene resolved IVY-1022.
--------------------------------

         Assignee: Maarten Coene
    Fix Version/s: 2.2.0-RC1
       Resolution: Duplicate

I think this seems a duplicate of IVY-1159 which should be fixed now.
Please reopen if I'm mistaken here...

Maarten

> 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
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> 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.


Mime
View raw message