[
https://issues.apache.org/jira/browse/IVY-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678656#action_12678656
]
Martin Eigenbrodt commented on IVY-1037:
----------------------------------------
A Workaround that is not to hard to implement is to allow the resovler
attribute to contain a Comma or space seperated list of
multiple resolvers. Users could than specify the individual resolvers.
However I'd prefere a "real" solution.
2009/3/4 Xavier Hanin (JIRA) <[email protected]>
> 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.
