[
https://issues.apache.org/jira/browse/IVY-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601911#action_12601911
]
Xavier Hanin commented on IVY-825:
----------------------------------
I've just added a junit test and a fix for this. Could you confirm it works for
you?
> dynamic resolveMode not being dynamic on branch
> -----------------------------------------------
>
> Key: IVY-825
> URL: https://issues.apache.org/jira/browse/IVY-825
> Project: Ivy
> Issue Type: Bug
> Reporter: Shawn Castrianni
> Assignee: Xavier Hanin
>
> Let's say I have an existing repository with published modules of (A branch A
> revision 1) being dependent on (B branch B revision 1) being dependent on (C
> branch C revision 1). Now I build a new C on a different branch C2 as
> revision 8 (doesn't really matter). If I then change my ivy settings file so
> that I have a module override for C to take branch C2 and resolveMode of
> dynamic, then when I get dependencies for A, I would expect to get this new
> revision 8 branch C2 version of C. Instead, the resolveMode of dynamic is
> properly changing the revision to look for latest.integration but it is
> keeping the old branch of C instead of C2. I was expecting the resolveMode
> of dynamic to allow dynamic branch names as well as revision numbers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
