lsp-java reports class in the same package as unresolved

[xqliu]

Describe the bug

1. lsp-java reports class in the same package as unresolved, and

2. when invoke lsp-execute-code-action, it promotes user to import the class, but since the two class is in the same package, so no import statement will be inserted,

3. and then lsp keeps shown the type as unresolved.

Expect: since the two class is in the same package, so no explicit import statement is needed and also lsp-java should not report the class definition as not found.

Actual: as described above.

Versions:

• Emacs: 27.0.90
• Lsp-mode: 6.2.1
• OS: Ubuntu 18.04

Thanks :)

[yyoncho]

Please provide a sample project to reproduce the issue with.

[xqliu]

Ok, I will provide a sample profile soon and try to reproduce the issue.

Thanks