[GRADLE-1182] Downloading [artifact]-[appendix]-[revision]-[classifier].[ext] not working. Created: 19/Oct/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug
Reporter: Thomas Glaeser Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Uploading an artifact with an appendix in the artifact name works quite well. However the download action seems to be not able to resolve artifacts with an appendix in its name ([module] != [artifact]-[appendix]).

Having a resolver defined like this

repositories {
    def baseUrl = 'http://url.to.artifact.repo'
    add(new org.apache.ivy.plugins.resolver.URLResolver()) {
        name = 'foo'
        m2compatible = true
        addIvyPattern(      baseUrl + '/[organisation]/[module]/[revision]/ivy(-[revision]).xml')
        addArtifactPattern( baseUrl + '/[organisation]/[module]/[revision]/[artifact](-[appendix])-[revision](-[classifier]).[ext]')
        descriptor = 'optional'
    }
}

and then trying to download it by

configurations {
    foo
}
dependencies {
    foo(group: 'group.name', name: 'module-name', appendix: 'feature', version: '1.2.3-SNAPSHOT', ext: 'jar') {
        appendix = 'feature'
        ext = 'jar'
    }
}
task(copy, type: Copy) {
    from configurations.foo
    into(buildDir)
}

will return the artifact without appendix only. The one having the appendix in its artifact name will not be downloaded. Looks like a bug!?

 Comments   
Comment by Thomas Glaeser [ 21/Oct/10 ]

Assigning a different configuration to each artifact seems to resolve the issue.

configurations {
    bas
    foo
}
dependencies {
    bas group: 'group.name', name: 'module-name', version: '1.2.3-SNAPSHOT', ext: 'jar', configuration: 'archives'
    foo group: 'group.name', name: 'module-name', appendix: 'feature', version: '1.2.3-SNAPSHOT', ext: 'jar', configuration: 'features'
}
task(cp, type: Copy) {
    from configurations.foo, configurations.bas
    into(buildDir)
}

Still looks like bug to me!?

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:49:04 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.