[GRADLE-1810] Provide a mutable FileTree Created: 26/Sep/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: New Feature
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

I've been looking for a FileTree that I can incrementally add base dirs to (cf. MutableFileCollection). Right now I have to use plus() which gives me a new FileTree and gets me into evaluation order troubles.



 Comments   
Comment by Adam Murdoch [ 07/Oct/11 ]

@peter, FileTree.plus() is lazy, so you can use it without worrying about evaluation order.

We should still provide a mutable implementation, though.

Comment by Peter Niederwieser [ 07/Oct/11 ]

What I needed was the ability to pass a FileTree to some other class and later add base dirs to it. Without that ability, my code became much more complex. The fact that FileTree.plus() is lazy didn't help here.

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