You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Jason Trump (JIRA)" <ji...@apache.org> on 2010/01/23 23:51:17 UTC

[jira] Created: (IVY-1163) add ability to programmatically change default resolver

add ability to programmatically change default resolver
-------------------------------------------------------

                 Key: IVY-1163
                 URL: https://issues.apache.org/jira/browse/IVY-1163
             Project: Ivy
          Issue Type: Improvement
          Components: Core
    Affects Versions: 2.1.0
            Reporter: Jason Trump
            Priority: Minor


I would like the ability to change the default resolver programmatically.  For example, from an Ant task.  The API exists for this (IvySettings.setDefaultResolver), but it does not work reliably.  The fix looks pretty easy.

When you call IvySettings.setDefaultResolver, it changes the value of "defaultResolverName", of type String.  However, it doesn't change the cache variable "defaultResolver".  So if you've called IvySettings.getDefaultResolver once, it will always return the original value, even if you later try to change it with setDefaultResolver.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-1163) add ability to programmatically change default resolver

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene updated IVY-1163:
-------------------------------

    Fix Version/s: 2.2.0-RC1
                       (was: trunk)

> add ability to programmatically change default resolver
> -------------------------------------------------------
>
>                 Key: IVY-1163
>                 URL: https://issues.apache.org/jira/browse/IVY-1163
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.1.0
>            Reporter: Jason Trump
>            Assignee: Maarten Coene
>            Priority: Minor
>             Fix For: 2.2.0-RC1
>
>         Attachments: ivy-1163-r902503.patch
>
>
> I would like the ability to change the default resolver programmatically.  For example, from an Ant task.  The API exists for this (IvySettings.setDefaultResolver), but it does not work reliably.  The fix looks pretty easy.
> When you call IvySettings.setDefaultResolver, it changes the value of "defaultResolverName", of type String.  However, it doesn't change the cache variable "defaultResolver".  So if you've called IvySettings.getDefaultResolver once, it will always return the original value, even if you later try to change it with setDefaultResolver.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (IVY-1163) add ability to programmatically change default resolver

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene resolved IVY-1163.
--------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Maarten Coene

Applied you patch in SVN trunk.
Thanks a lot for the contribution!

> add ability to programmatically change default resolver
> -------------------------------------------------------
>
>                 Key: IVY-1163
>                 URL: https://issues.apache.org/jira/browse/IVY-1163
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.1.0
>            Reporter: Jason Trump
>            Assignee: Maarten Coene
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: ivy-1163-r902503.patch
>
>
> I would like the ability to change the default resolver programmatically.  For example, from an Ant task.  The API exists for this (IvySettings.setDefaultResolver), but it does not work reliably.  The fix looks pretty easy.
> When you call IvySettings.setDefaultResolver, it changes the value of "defaultResolverName", of type String.  However, it doesn't change the cache variable "defaultResolver".  So if you've called IvySettings.getDefaultResolver once, it will always return the original value, even if you later try to change it with setDefaultResolver.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-1163) add ability to programmatically change default resolver

Posted by "Jason Trump (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Trump updated IVY-1163:
-----------------------------

    Attachment: ivy-1163-r902503.patch

patch with failing test case and a proposed fix.

> add ability to programmatically change default resolver
> -------------------------------------------------------
>
>                 Key: IVY-1163
>                 URL: https://issues.apache.org/jira/browse/IVY-1163
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.1.0
>            Reporter: Jason Trump
>            Priority: Minor
>         Attachments: ivy-1163-r902503.patch
>
>
> I would like the ability to change the default resolver programmatically.  For example, from an Ant task.  The API exists for this (IvySettings.setDefaultResolver), but it does not work reliably.  The fix looks pretty easy.
> When you call IvySettings.setDefaultResolver, it changes the value of "defaultResolverName", of type String.  However, it doesn't change the cache variable "defaultResolver".  So if you've called IvySettings.getDefaultResolver once, it will always return the original value, even if you later try to change it with setDefaultResolver.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.