[GRADLE-1404] Remove the 'master' naming convention in flat multi-project builds Created: 27/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Kevin Stembridge Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Section 35.4 of the user guide describes the rules for determining whether a project is a subproject of a multi-project build or not. Basically, if there is no settings.gradle file in the current directory it looks for one in a sibling directory named 'master'.

I'm not sure if there is a good reason for enforcing this naming convention. Could it be possible to search all sibling directories for the settings.gradle file and report an error if there is more than one?

The reason for wanting to remove this restriction is to allow us to have multiple multi-project builds in a given Eclipse workspace. I know the name of the Eclipse project doesn't have to be the same as the name of the underlying directory but it just adds confusion and requires extra work. It also adds complexity if the .project files are generated.

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