Skip to content

Eclipse annotation processing is broken in v1.49.0 #4278

Closed
eclipse-jdtls/eclipse.jdt.ls
#3630

Description

@ChrisTrenkamp

I have a multi-project Gradle project that uses the eclipse and the https://github.com/diffplug/goomph apt plugins. The project is set up with the eclipse task to generate the .classpath and .project Eclipse files for each project.

Up to v1.48.0, this has worked. In the v1.49.0 release, something broke the annotation processing. I should see a bunch of generated builder objects in each subproject's apt_generated directories, but each project only has one generated builder object, if it has any generated sources at all. It's as if the annotation processing stops at the first Java file.

I took a look at the diff between v1.47.0 and v1.49.0, and there doesn't seem to be any particular change that stands out to me that might have affected the annotation processing. I'm not sure what to look for.

Activity

  1. fbricon commented on Dec 3, 2025

    @fbricon
    Collaborator

    Can you provide a sample project reproducing this issue?

  2. ChrisTrenkamp commented on Dec 3, 2025

    @ChrisTrenkamp
    Author

    vscode-buildship-annotation-processor-issue.zip

    Here's a reproducer. Run ./gradlew eclipse to generate the Eclipse settings, and then open the project in VSCode with the Java extension pack running.

    In v1.48, it works correctly. The .apt_generated directory generates the builder classes and the language server finds all the class definitions.

    Then upgrade the extension to v1.50, run ./gradlew clean cleanEclipse, ./gradlew eclipse, and clean the workspace. Now the .apt_generated directory is empty. I'm not sure if the annotation processor is not running, or if the generated classes are being placed elsewhere.

  3. jackrein commented on Dec 4, 2025

    @jackrein

    I am also running into this issue. Using v1.48.0 works, but after upgrading to v1.49.0 or v1.50.0 I am seeing unresolved imports for generated classes.

  4. jackrein commented on Dec 16, 2025

    @jackrein
  5. fbricon commented on Dec 19, 2025

    @fbricon
    Collaborator

    you can try the latest vscode-java pre-release, that includes the fix for this annotation processing bug.

  6. added this to the Early January 2026 milestone on Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions