Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <973338458.1237329111727.JavaMail.jira@brutus>
Date: Tue, 17 Mar 2009 15:31:51 -0700 (PDT)
From: "Maarten Coene (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVY-1037) Buildnumber task does not work for
 chained resolvers
In-Reply-To: <1582079048.1235987412802.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Maarten Coene updated IVY-1037:
-------------------------------

    Fix Version/s:     (was: trunk)
                   2.0.1

> Buildnumber task does not work for chained resolvers
> ----------------------------------------------------
>
>                 Key: IVY-1037
>                 URL: https://issues.apache.org/jira/browse/IVY-1037
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant, Core
>            Reporter: Martin Eigenbrodt
>            Assignee: Maarten Coene
>             Fix For: 2.0.1
>
>         Attachments: IVY1037.patch
>
>
> If the resolver attribute of the  buildnumber task point to a chained resolver the buildnumber task will not find any existing revision.
> I will attach a unittest to show the problem.
> I've debuged into this point:
> The Buildnubmer task uses SearchEngine.listModules whcih in turn uses
> Resolver.listTokenValues. The Doc says ListTokenValue must not return values for child resolvers. 
> So litTokenValues can not  return values for child resolvers either. I don't know how to fix.

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