[
https://issues.apache.org/jira/browse/IVY-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840010#comment-16840010
]
jaikiran pai commented on IVY-1603:
-----------------------------------
Hello [~Simon Wade], I forgot to update this issue earlier. I did test the
reproducer you attached and I do see what's happening. However, the failure is
expected (since the dependency does specify a branch but the ivy of the
dependency has a branch, even if an empty one). The place to fix this correctly
is to not set the branch to an empty string in first place in the ivy.xml. For
that to be fixed, I need to understand what/how that ivy.xml with an empty
branch got generated in first place. Do you know what/how that was created?
I will also see if we can improve this error message a bit to indicate the
mismatch of the branch which is causing this issue.
> Latest version matcher fails when found branch is empty
> -------------------------------------------------------
>
> Key: IVY-1603
> URL: https://issues.apache.org/jira/browse/IVY-1603
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5.0-rc1
> Reporter: Simon Wade
> Assignee: jaikiran pai
> Priority: Major
> Attachments: IVY-1603.patch, IVY-1603.zip
>
>
> Resolving a latest.integration revision fails when the found dependency
> contains an empty string for a branch. The cryptic error message looks
> something like:
> {noformat}
> [ivy:resolve] java.text.ParseException: inconsistent module descriptor file
> found in '[redacted]ivy-3.1.4-rc5.xml': bad revision: expected='3.1.4-rc5'
> found='3.1.4-rc5';
> {noformat}
>
> This issue doesn't appear to be present in 2.4.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
