[GRADLE-991] Add support for extra Ivy dependency pattern elements Created: 18/Jun/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Alex Antonov Assignee: Unassigned
Resolution: Won't Fix Votes: 3


 Description   

Provide an ability to define extra artifact attributes to an already existing group, name and version
Ivy also supports the module and branch pattern attributes, which are commonly used in companies that are already using pure Ivy based Ant builds.

To make things more generic, it would be nice to add support to the dependency declaration in such a way, that there is an ability to add other arbitrary properties to the artifact, i.e.

compile group: 'javax.servlet', name: 'servlet-api', version: '2.5', projectname: "tomcat"

where projectname is an added attribute.
Then have an ability to map that into an Ivy pattern when using a resolver, so that the value of projectname attribute can be used as a url segment delimiter or in some other ways that might come up.

repositories {
    add(new org.apache.ivy.plugins.resolver.FileSystemResolver()) {
        name = 'repo'
        addIvyPattern "$projectDir/repo/[organisation]/[projectname]/[module]-ivy-[revision].xml"
        addArtifactPattern "$projectDir/repo/[organisation]/[projectname]/[module]-[revision](-[classifier]).[ext]"
        descriptor = 'optional'
        checkmodified = true
    }
}

Relates to GRADLE-197

 Comments   
Comment by Hans Dockter [ 27/Jul/10 ]

Sorry, Alex that this feature does not make it into 0.9. We will tackle the dependency DSL in the first 1.0 milestone (for which we plan 4 week cycles).

Comment by Phil Messenger [ 04/Aug/11 ]

Has there been any progress with this?

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:44:06 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.