Skip to content

[build] Settings.gradle's logic to handle different buildFile name could result in phantom subproject #16322

Closed
@guesshe

Description

Expected Behavior
Regardless of the buildFile names, no phantom subprojects should be created.
 

If a subproject has a default buildFile name like build.grade, the build setup should NOT create a phantom subproject.
 
Current Behavior
If a new subproject is added in with structure like this spring-security-foo/spring-security-foo-bar, using a default buildFile name build.gradle under spring-security-foo-bar will result in the creation of a phantom subproject spring-security-foo.

No phantom subproject should be created due to the name change of the buildFile.

Context
Settings.gradle should be updated to give a consistent behavior for different buildFile names.

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions