You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Martin Eigenbrodt (JIRA)" <ji...@apache.org> on 2009/01/27 11:14:59 UTC

[jira] Created: (IVY-1019) resolver attribute for buildnumber task

resolver attribute for buildnumber task
---------------------------------------

                 Key: IVY-1019
                 URL: https://issues.apache.org/jira/browse/IVY-1019
             Project: Ivy
          Issue Type: Improvement
          Components: Ant
            Reporter: Martin Eigenbrodt


Teh BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.

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


[jira] Assigned: (IVY-1019) resolver attribute for buildnumber task

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

Maarten Coene reassigned IVY-1019:
----------------------------------

    Assignee: Maarten Coene

> resolver attribute for buildnumber task
> ---------------------------------------
>
>                 Key: IVY-1019
>                 URL: https://issues.apache.org/jira/browse/IVY-1019
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>            Reporter: Martin Eigenbrodt
>            Assignee: Maarten Coene
>         Attachments: ivy-1019.patch
>
>
> Teh BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.

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


[jira] Updated: (IVY-1019) resolver attribute for buildnumber task

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

Maarten Coene updated IVY-1019:
-------------------------------

    Fix Version/s:     (was: trunk)
                   2.0.1

> resolver attribute for buildnumber task
> ---------------------------------------
>
>                 Key: IVY-1019
>                 URL: https://issues.apache.org/jira/browse/IVY-1019
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>    Affects Versions: 2.0
>            Reporter: Martin Eigenbrodt
>            Assignee: Maarten Coene
>             Fix For: 2.0.1
>
>         Attachments: ivy-1019.patch
>
>
> The BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.

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


[jira] Updated: (IVY-1019) resolver attribute for buildnumber task

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

Maarten Coene updated IVY-1019:
-------------------------------

          Description: The BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.  (was: Teh BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.)
    Affects Version/s: 2.0
        Fix Version/s: trunk

> resolver attribute for buildnumber task
> ---------------------------------------
>
>                 Key: IVY-1019
>                 URL: https://issues.apache.org/jira/browse/IVY-1019
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>    Affects Versions: 2.0
>            Reporter: Martin Eigenbrodt
>            Assignee: Maarten Coene
>             Fix For: trunk
>
>         Attachments: ivy-1019.patch
>
>
> The BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.

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


[jira] Resolved: (IVY-1019) resolver attribute for buildnumber task

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

Maarten Coene resolved IVY-1019.
--------------------------------

    Resolution: Fixed

Applied your patch into svn trunk and updated the documentation.
Thanks a lot for the contribution!

Maarten

> resolver attribute for buildnumber task
> ---------------------------------------
>
>                 Key: IVY-1019
>                 URL: https://issues.apache.org/jira/browse/IVY-1019
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>    Affects Versions: 2.0
>            Reporter: Martin Eigenbrodt
>            Assignee: Maarten Coene
>             Fix For: trunk
>
>         Attachments: ivy-1019.patch
>
>
> The BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.

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


[jira] Updated: (IVY-1019) resolver attribute for buildnumber task

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

Martin Eigenbrodt updated IVY-1019:
-----------------------------------

    Attachment: ivy-1019.patch

This patch adds the wanted behaviour to the buildnumber task.

> resolver attribute for buildnumber task
> ---------------------------------------
>
>                 Key: IVY-1019
>                 URL: https://issues.apache.org/jira/browse/IVY-1019
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>            Reporter: Martin Eigenbrodt
>         Attachments: ivy-1019.patch
>
>
> Teh BuildNumber Task should have an resolver Attribute that allows to specify a resovler used for searching existing versions. Currently the task looks at all configured resolvers. This is a performance issue in our environment where we have different "views" of the same repository (url, filesystem, ssh)  and the correct view is picked depending on where the build happens.

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