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

Anthony Hsu commented on GROOVY-8372:
-------------------------------------

[~paulk], could you take another look – I've attached a zip that reproduces the 
issue.

> GrapeIvy downloads wrong artifact for non-default conf when artifact name is 
> not the same as the module
> -------------------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-8372
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8372
>             Project: Groovy
>          Issue Type: Bug
>          Components: Grape
>    Affects Versions: 2.2.2
>            Reporter: Anthony Hsu
>            Priority: Trivial
>         Attachments: grapesTest.zip
>
>
> In my Ivy repo, there exists the following directory with the following 
> contents:
> {noformat}
> com/example/foo/bar/1.2.3/
>   bar-1.2.3.jar
>   bar-1.2.3.ivy
>   bar-qux-1.2.3.jar
> {noformat}
> In bar-1.2.3.ivy, the following conf and publication exist:
> {noformat:title=bar-1.2.3.ivy}
> ...
> <configurations>
>   <conf name="qux"/>
>   ...
> </configurations>
> ...
> <publications>
>   <artifact name="bar" type="jar" ext="jar" 
> conf="apiElements,archives,runtime,runtimeElements"/>
>   <artifact name="bar-qux" type="jar" ext="jar" conf="qux"/>
>   ...
> </publications>
> ...
> {noformat}
> When I try to use Grape to resolve bar-qux-1.2.3.jar by setting
> * org = com.example.foo
> * module = bar
> * version = 1.2.3
> * conf = qux
> bar-1.2.3.jar gets downloaded instead of bar-qux-1.2.3.jar.
> This issue seems to be caused by GROOVY-6470. The correct jar 
> (bar-qux-1.2.3.jar) gets downloaded when using groovy-all-2.2.1, but the 
> wrong jar is downloaded when using groovy-all-2.2.2 and newer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to