You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Simon Wade (JIRA)" <ji...@apache.org> on 2019/03/01 01:23:00 UTC

[jira] [Commented] (IVY-1603) Latest version matcher fails when found branch is empty

    [ https://issues.apache.org/jira/browse/IVY-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781166#comment-16781166 ] 

Simon Wade commented on IVY-1603:
---------------------------------

I've attached a patch for LatestVersionMatcher.java that works for me. I haven't yet reproduced the issue outside of my work environment, but I could potentially put together a standalone test if needed.

> 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
>            Priority: Major
>         Attachments: IVY-1603.patch
>
>
> 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)