ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-691) use ModuleRevisionId instead of ModuleId in IvySettings#getResolver
Date Fri, 04 Jan 2008 17:09:33 GMT

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

Xavier Hanin resolved IVY-691.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-2

I've made the change, and updated the settings parser to be able to use this new feature.
Usage is documented in the configuration/module page.

> use ModuleRevisionId instead of ModuleId in IvySettings#getResolver
> -------------------------------------------------------------------
>
>                 Key: IVY-691
>                 URL: https://issues.apache.org/jira/browse/IVY-691
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0.0-beta-2
>
>
> Currently to get the dependency resolver for a module one use the IvySettings#getResolver(ModuleId
moduleId). 
> Checking the current usage of this method, all callers actually have a ModuleRevisionId
when calling the method. Using the ModuleRevisionId instead of the ModuleId would allow more
specific resolver assignment, like resolvers depending on the version (this require to be
careful since the version may not be resolved yet when asking) and also resolvers depending
on extra attributes which open the door to many use cases.

-- 
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