Under certain circumstances, .project will cause projects to be recognized as nested.

[kilesduli]

I confirm that...

• I have searched the issue tracker, documentation, FAQ, Discourse, and Google, in case this issue has already been reported/resolved.

• I have read "How to Debug Issues", and will use it to provide as much information about this issue as possible.

• The issue can be reproduced on the latest available commit of Doom.

• The issue can be reproduced on a stable release of Emacs, such as 27, 28, or 29. (Unstable versions end in .50, .60, or .9x)

Expected behavior

.project won't be treated as project marker in doom.

Current behavior

The java language server 'jdtls' will add .project in subdirectory when directory layout like this.

.
├── app
│   ├── build.gradle.kts
│   ├── .classpath
│   ├── .project  <-----
│   └── src
├── gradlew
├── gradlew.bat
├── .project    <-----
└── settings.gradle.kts

But doom will treat .project in the folder as a project marker. The app folder will became a known project in projectile.

doomemacs/lisp/doom-projects.el

Lines 84 to 88 in 9620bb4

	(setq projectile-project-root-files-bottom-up
	(append '(".projectile" ; projectile's root marker
	".project" ; doom project marker
	".git") ; Git VCS root dir
	(when (executable-find "hg")

I think the project marker .project is duplicated with .projectile, and the latter is more general.

Steps to reproduce

1. Use gradle init --type java-application --dsl kotlin --package local.duli --project-name test --java-version 17 --no-split-project generate directory layout.
2. Use latest java language server jdtls.
3. open a java source file which in app folder.
4. SPC p f will see app treated as projectile project.

System Information

https://pastebin.com/8ACQDc8U