[
https://issues.apache.org/jira/browse/IVY-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098632#comment-17098632
]
Simon Wade commented on IVY-1603:
---------------------------------
Hi [~jaikiran] , my apologies for ignoring this for so long! In this case, the
ivy.xml with the empty branch name was generated by another team at the company
I used to work for; loosely speaking, they produced the Ivy artifacts, and I
consumed them.
As you might expect, I was able to work around this by inserting branch="" when
specifying my dependencies. :D
If it makes sense to consider an empty string as a valid branch name (I'm not
familiar enough with Ivy to be qualified to comment any further on that!), then
I think your suggestion of improving the error message would be enough to close
this.
Thanks!
> 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
(v8.3.4#803005)
