[GRADLE-2798] SourceDirectorySet.srcDirs(Object...) does not flatten args Created: 20/Jun/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I would expect the following to work:

sourceSets {
  main {
    resources {
      srcDirs java.srcDirs
      exclude '**/*.xml'

Basically, I'd expect the srcDirs(Object...) method to behave like Project.files() with regard to unpacking collections.

Comment by Gradle Forums [ 20/Jun/13 ]

It should be:

apply plugin: 'groovy'
sourceSets {
main {
resources {
srcDirs java.srcDirs
exclude '*/.xml'

Using the source method means that the other source directory set should be included wholesale (i.e. includes/excludes don't apply).

Comment by Gradle Forums [ 20/Jun/13 ]

No, I had tried that before, there is even a post by me asking somewhere in this forum. What I get is:

$ g clean processResources
Converting class java.util.LinkedHashSet to File using toString() method has been deprecated and is scheduled to be removed in Gradle 2.0. Please use java.io.File, java.lang.String, java.net.URL, or java.net.URI instead.


Total time: 6.801 secs
$ find -type f build/resources/

Which means that src/java is not included in resources. If you want it this way, you actually need to do it like this:

srcDirs java.srcDirs as File[]


srcDirs = srcDirs + java.srcDirs

I don't like the looks of the former, and I've just came up with the latter ;d That's why I went on to search deeper and found 'source'.
I guess I will have to live with one of the two. I do understand the reasoning behind 'source' being wholesale, it was just surprising at first, and it should probably be documented that such 'sourcing' is not affected by further configuration.


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