Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <823387862.1235987892816.JavaMail.jira@brutus>
Date: Mon, 2 Mar 2009 01:58:12 -0800 (PST)
From: "Martin Eigenbrodt (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12677942#action_12677942 ] 

Martin Eigenbrodt commented on IVY-1037:
----------------------------------------

The Diff was made against the test Dir of the current trunkt.

> 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
>            Reporter: Martin Eigenbrodt
>             Fix For: trunk
>
>         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.