You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2014/03/26 23:04:24 UTC

[jira] [Closed] (IVY-1436) Backslash in ivy.xml /ivy-module/publications/artifact/@name breaks retrieval

     [ https://issues.apache.org/jira/browse/IVY-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene closed IVY-1436.
------------------------------


> Backslash in ivy.xml /ivy-module/publications/artifact/@name breaks retrieval
> -----------------------------------------------------------------------------
>
>                 Key: IVY-1436
>                 URL: https://issues.apache.org/jira/browse/IVY-1436
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0, 2.3.0, 2.4.0
>            Reporter: Jerry Maloney
>              Labels: artifact, patch, retrieval, url
>         Attachments: FixURLResolverUnitTests.patch, NormalizeBackslash.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I have defined a URL resolver that includes, among others, the artifact pattern {{<artifact pattern="http://repo1:8081/artifactory/ext-repackaged-local/[organization]/[module]/[revision]/[type]/[artifact]-[revision].[ext]" />}} as well as an ivy pattern. The ivy file resolves properly, but it includes a published artifact with the defintion {{<artifact name="en\PresentationUI" type="xml" ext="xml" extra:os="windows" conf="default"/>}}. This ivy file has been in our artifact repository for a long time and cannot be changed.
> My issue occurs when ivy tries to retrieve this particular artifact. It uses the URL {{http://repo1:8081/artifactory/ext-repackaged-local/com/Microsoft/ReferenceAssemblies/3.0.6920.5001/xml/en\PresentationUI-3.0.6920.5001.xml}} which does not resolve due to the backslash between {{en}} and {{PresentationUI}}.
> I propose that ivy should fix URLs like this by replacing \ with /. I already have a fix ready to go which I'll use in my situation, but I would like this change to be accepted in the project.



--
This message was sent by Atlassian JIRA
(v6.2#6252)