Visitar URL original
[1.56.0] Lots of AWS Java sdk related intellisense is broken · Issue #4500 · redhat-developer/vscode-java · GitHub
Skip to content

[1.56.0] Lots of AWS Java sdk related intellisense is broken #4500

Description

@tokidoki11

Describe the bug

I noticed version 1.56.0 reports errors for lots of my code related to AWS SDK

To Reproduce
Steps to reproduce the behavior:
I simply just updated vscode-java to version 1.56.0

Image Image

Expected behavior

No code error reported as in version 1.55.0

Image

Environment

  • Operating System: MacOS - running devcontainer with debian-trixie
  • JDK version: 21
  • Visual Studio Code version: 1.133.0
  • Java extension version: 1.56.0

Additional Information

Activity

  1. wenytang-ms commented on Sep 7, 2026

    @wenytang-ms
    Contributor

    @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:

    1. The exact AWS SDK version and your Maven/Gradle dependency tree.
    2. Whether the project compiles successfully with mvn compile or gradle compileJava.
    3. Whether the problem remains after running Java: Clean Java Language Server Workspace.
    4. 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?

    GetParametersByPathRequest request = GetParametersByPathRequest.builder()
        .path(parameterPrefix)
        .withDecryption(true)
        .recursive(false)
        .build();
    
    GetParametersByPathIterable paginator =
        ssmClient.getParametersByPathPaginator(request);

    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.

  2. tokidoki11 commented on Sep 7, 2026

    @tokidoki11
    Author

    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

    1. software.amazon.awssdk:ssm:2.42.26
    2. compilejava via gradle is fine
    3. Tried on the 1.56.0 still happens, 1.55.0 is fine as state
    4. Here is the sanitized log Class name : ParameterStoreConfig

    sanitized-log.txt

    Separating as a variable is still showing error
    Image

  3. wenytang-ms commented on Sep 8, 2026

    @wenytang-ms
    Contributor

    I can repro such issue, and submit the fix pr into jdt.core
    eclipse-jdt/eclipse.jdt.core#5373

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions