Chore: Centralize generated content#34
Conversation
| .map(|name| name == ".bazelproject") | ||
| .map(|name| name == crate::internal_config::config_file()) | ||
| .unwrap_or(false) | ||
| && is_in_bazel_jdt_dir(path) |
There was a problem hiding this comment.
is_bazelproject_file should check both the name and the location
96a1b88 to
3429a1d
Compare
7deb1da to
425c371
Compare
|
Hi, @kduy969 It is recommended that when generating the |
|
After loading examples/simple-java-project, Java Unit Explorer did not find any targets. Below is my .bazeproject file configuration. |
ok, let me put this behavior back |
|
I got the same issue as @kduy969, the Unit Test Codelens and Test explorer disappeared:
|
|
How about we continue use folder |
@zhirui1994 Actually, I didn't want to share a directory with previous plugins, which necessitated adding logic to clear the previous directory. |
Got it, makes sense. |
|
@kduy969 I think the logic for |

Introduces
config.jsonat the repo root as the SSOT for internal path constants (.bazel-jdt/, .bazelproject, projects/, aspects/), replacing all hardcoded strings across the stack:internal_configmodule reads via include_str! at compile timeconfig.jsoninto the JAR at build time;InternalConfigloads it from classpathGenerated files location changes:
Also create .gitignore inside .bazel-jdt folder to ensure all generated files are ignored