[
https://issues.apache.org/jira/browse/IVY-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678612#action_12678612
]
Martin Eigenbrodt commented on IVY-1037:
----------------------------------------
I would expect the buildnumbertask on a chained resovler to take in acount
all revisions.
Example:
ChainResolver
Resolver 1:
module "A" in Revision 4
Resolver 2
module "A" n Revision 2
<buildnumber resolver="ChainResolver"> should give "5" as next number.
I'm very into the ivy code but i Think there must be a way to ask a chained
resolver for all artifacts. Somethingh Like ListTokenValue but including
child.
2009/3/3 Maarten Coene (JIRA) <j...@apache.org>
> 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.
