[GRADLE-2260] Depenendcy artifact excludes DSL should allow type (like ivy exclude) Created: 30/Apr/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-1
Fix Version/s: None

Type: Improvement
Reporter: Jacob Aleksynas Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

Like this: therefore transitive dependencies will not bring along these types (just like the <exclude type=""/> of ivy files. 

compile(group: 'gap', name:'MyModule', version: '1.+') { 
   exclude type: 'source'
   exclude type: 'javadoc'
}

This is particularly painful when you do not control the modules (or the repository) of dependencies.

If a repo uses types, but not always confs (ivy standard layout) then you get a large number of artifacts with conflicting names (source/classes jar will have the same name in WEB-INF/lib for example)

 Comments   
Comment by Scott Hickey [ 23/Jan/14 ]

It would be good if this worked for the dependency itself. If there is a sources.zip or javadocs.zip in an Ivy repository as par of the dependency specified, it would be very helpful to indicate that only the jar is a compile time / runtime dependency. Without this feature, the source and doc .zip files can end up on the classpath, which in my app causes a runtime error when using applicationPlugin's run task.

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 12:17:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.