[GRADLE-338] Remove the settings file Created: 28/Dec/08  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Won't Fix Votes: 3

Issue Links:
Related to GRADLE-416 Merge Project and ProjectDescriptor Resolved
dependent on GRADLE-519 Allow build script classpath to be sp... Resolved

Comment by Jon Cox [ 22/Jan/09 ]

It''s kind of nice to be able to include/exclude subproject from a master build.
What will take the place of that when the gradle.settings file is gone?

Comment by Adam Murdoch [ 23/Jan/09 ]

We're still discussing this - probably the build file. I don't think we would remove the ability to do anything that you can currently with the settings file.

Comment by Steve Ebersole [ 04/Jun/10 ]

Except perhaps the ability to name the build file.

Comment by Jordan Zimmerman [ 29/Oct/11 ]

+1 Requiring settings.gradle for multi-project builds is very ugly. I'd like to see one file: build.gradle.

Comment by Suminda Dharmasena [ 23/Dec/11 ]

I am up for merging settings functionality with build

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