[
https://issues.apache.org/jira/browse/IVY-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750381#action_12750381
]
Willem Verstraeten commented on IVY-1116:
-----------------------------------------
Also, if a custom resolveId is set, shouldn't it be treated as a pattern ? Ie.
to work around the issue for now, I'd like to set the resolveId to
[org]-[module]-[branch] myself in the ant task, but the resolveId is not
treated as a pattern so the [] parts are not replaced by the actual values. I
can work around that by using the <ivy:info/> ant task, but that shouldn't be
necessary.
See
http://www.nabble.com/How-to-set-the-resolve-ID-for-an-inline-resolve-td25217711.html
for a more detailed explanation.
> Make default resolveId include branch
> -------------------------------------
>
> Key: IVY-1116
> URL: https://issues.apache.org/jira/browse/IVY-1116
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.1.0-RC2
> Reporter: Willem Verstraeten
>
> By default, the resolveId is [org]-[module], but it would make sense to make
> this [org]-[module]-[branch]. When you use branches, it is very possible that
> the same ivy module is built for two branches at the same time. With the
> default resolveId this gives concurrency issues, but if the resolveId would
> include the branch name by default, these problems would not exist.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
