[GRADLE-714] Allow tasks to use files with a specific 'ivy type' from a configuration Created: 22/Oct/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Ross Black Assignee: Unassigned
Resolution: Won't Fix Votes: 4


 Description   

Allow some way for tasks (eg compile) and other code to specify that they use a subset of files from a configuration based on ivy type.

eg Using an existing ivy repository that uses ivy types to group files within a single configuration:
ivy.xml snippet
–

<configurations>
<conf name="default"/>
</configurations>
<publications>
<artifact name="junit"
type="jar"
conf="default"/>
<artifact name="junit-src"
type="source"
ext="zip"
conf="*"/>
<artifact name="junit-license"
type="license"
ext="html"
conf="*"/>
</publications>
–

Currently the compile tasks will include the jar, the source zip, and the html licence on the classpath.

It appears as if the only way to extract the files files by ivy type is similar to the following gradle code:
–

task resolve << {

Set<ResolvedArtifact> artifacts = configurations.testCompile.resolvedConfiguration.resolvedArtifacts

def typedArtifacts = artifacts.findAll

{ artifact -> artifact.type == 'license' }

println("Artifacts = " + ResolvedDependencies.getFilesFromArtifacts(typedArtifacts))
}

–

 Comments   
Comment by Jacob Aleksynas [ 30/Apr/12 ]

An
exclude type: 'source'
and/or
include type: 'jar'

would be a welcome addition to the DSL.

particularly with large existing repositories that have heavily leveraged the type in ivy.

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