Project structure issues

[runchen0919]

Description:

When my project structure directory is as shown below, there are only BUILD files and directories in my directory, but no Java files.

| - src
    | - java
        | - com
            | - demo
                | - BUILD
                | - folder1
                | - folder2

The plugin will display the following error message:

[Error - 16:57:20] 1 Dec 2025, 4:57:20 pm src/java/com/demo/xxx [in __main__] does not exist
Java Model Exception: Error in Java Model (code 969): src/java/com/demo/xxx [in __main__] does not exist
	at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:548)
	at org.eclipse.jdt.internal.core.PackageFragmentRoot.getUnderlyingResource(PackageFragmentRoot.java:768)
	at org.eclipse.jdt.internal.core.PackageFragment.getUnderlyingResource(PackageFragment.java:417)
	at org.eclipse.jdt.internal.core.Openable.getUnderlyingResource(Openable.java:333)
	at org.eclipse.jdt.internal.core.CompilationUnit.getUnderlyingResource(CompilationUnit.java:1095)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDiagnosticsHandler.collectNonJavaProblems(BaseDiagnosticsHandler.java:198)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDiagnosticsHandler.endReporting(BaseDiagnosticsHandler.java:149)
	at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.reportProblems(ReconcileWorkingCopyOperation.java:157)
	at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:126)
	at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:751)
	at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:816)
	at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1431)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.publishDiagnostics(BaseDocumentLifeCycleHandler.java:338)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.publishDiagnostics(BaseDocumentLifeCycleHandler.java:301)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler$PublishDiagnosticJob.run(BaseDocumentLifeCycleHandler.java:798)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

[runchen0919]

@guw Regarding the issue of unsupported project structure, I analyzed the code logic. The following code logic checks the packageName based on the Java file. I tried adding the missing path to execute this part of the logic during debugging. After the project loads, the navigation function works correctly.

    private IPath detectPackagePath(JavaSourceEntry fileEntry) {
        // we inspect at most one file per directory (anything else is too weird to support)
        var parentPath = fileEntry.getPathParent();
        var previouslyDetectedPackagePath = detectedPackagePathsByFileEntryPathParent.get(parentPath);
        if (previouslyDetectedPackagePath != null) {
            return previouslyDetectedPackagePath;
        }

        // read package from .java file
        var packageName = readPackageName(fileEntry);
......

Therefore, I'm wondering if it's possible to add logic to detect this directory structure (no Java files in the same directory as the BUILD file), adding this path to the detection path and executing subsequent logic after detectPackagePath.

This would support this project directory structure. I'm not sure if this is reasonable, or do you have a better solution?

[guw]

Can you provide an example of the actual target setup? A little test workspace exposing the problem as PR here: https://github.com/eclipseguru/bazel-eclipse/tree/main/bundles/testdata/workspaces

[runchen0919]

@guw I actually created a test module for this problem. 7c007aa