You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[1.56.0] Lots of AWS Java sdk related intellisense is broken #4500
I tried to reproduce the issue with the code shown in the screenshots, using both the JDT Core compiler bundled with vscode-java 1.55.0 and the one bundled with 1.56.0. I also tested with AWS SDK for Java versions 2.32.32 and 2.54.13, but the code compiled successfully in all cases.
Please provide a minimal reproducible project? If that is not possible, the following information would help:
The exact AWS SDK version and your Maven/Gradle dependency tree.
Whether the project compiles successfully with mvn compile or gradle compileJava.
Whether the problem remains after running Java: Clean Java Language Server Workspace.
The Java Language Server log, available through Java: Open Java Language Server Log File.
As an additional test, please check whether the error still occurs after extracting the request into an explicitly typed local variable?
This would help determine whether the problem is specifically caused by type inference for the chained builder expression. The screenshot suggests that the request expression may be incorrectly inferred as the parent type SsmRequest, but we need a reproducible project or the dependency details to determine whether this is a JDT Core regression or a project-import/classpath issue.
Activity
wenytang-ms commentedon Sep 7, 2026
@tokidoki11 Thanks for reporting this.
I tried to reproduce the issue with the code shown in the screenshots, using both the JDT Core compiler bundled with vscode-java 1.55.0 and the one bundled with 1.56.0. I also tested with AWS SDK for Java versions 2.32.32 and 2.54.13, but the code compiled successfully in all cases.
Please provide a minimal reproducible project? If that is not possible, the following information would help:
mvn compileorgradle compileJava.Java: Clean Java Language Server Workspace.Java: Open Java Language Server Log File.As an additional test, please check whether the error still occurs after extracting the request into an explicitly typed local variable?
This would help determine whether the problem is specifically caused by type inference for the chained builder expression. The screenshot suggests that the request expression may be incorrectly inferred as the parent type
SsmRequest, but we need a reproducible project or the dependency details to determine whether this is a JDT Core regression or a project-import/classpath issue.tokidoki11 commentedon Sep 7, 2026
Thanks for responding for the issue im facing
I think reproducing with my current project size is quite difficult. I wonder if this would be enough
sanitized-log.txt
Separating as a variable is still showing error

wenytang-ms commentedon Sep 8, 2026
I can repro such issue, and submit the fix pr into jdt.core
eclipse-jdt/eclipse.jdt.core#5373
Preserve covariant return types when merging null annotations
Preserve covariant return types when merging null annotations (#5373)
wenytang-ms commentedon Oct 12, 2026
@jjohnstn the fix pr is merged, please close this issue