@SuperBuilder with Custom TestBuilder Causes Syntax Highlighting Issue in VSCode for Java

When using Lombok’s @SuperBuilder in a Test class and defining a custom TestBuilder to add more methods, VSCode’s syntax highlighting fails. The class colors are incorrectly rendered, and it appears the IDE no longer correctly interprets the structure of the class. This only occurs after adding the custom builder; without it, highlighting works as expected.

Environment

• Operating System: macOS 15.0.1
• JDK version: OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode, sharing)
• Visual Studio Code version: 1.94.2
• Java extension version: v1.36.2024101808

Steps To Reproduce

1.	Create a class Test annotated with Lombok’s @SuperBuilder.
2.	Manually define a TestBuilder to add additional methods beyond the automatically generated builder.
3.	Open the project in VSCode and observe the syntax highlighting for the Test class.

import com.google.common.collect.Lists;
import lombok.Data;
import lombok.NoArgsConstructor;
import lombok.experimental.SuperBuilder;

import java.util.List;

@SuperBuilder
@NoArgsConstructor
@Data
public abstract class Test {
    private List<String> exampleList;

    public abstract class TestBuilder<C extends Test, B extends Test.TestBuilder<C, B>> {
        public TestBuilder() {
            exampleList = Lists.newArrayList();
        }

        public void addExample(String example) {
            exampleList.add(example);
        }
    }
}

Current Result

VSCode’s syntax highlighting becomes incorrect when a custom TestBuilder is defined. The class colors are rendered improperly, and it seems the IDE fails to properly handle the class structure.

Expected Result

VSCode should continue to correctly render syntax highlighting, even when a custom TestBuilder is used with Lombok’s @SuperBuilder.

Additional Informations

Reproduce el problema usando la clase Java y el TestBuilder personalizado mostrados en el issue, con Lombok’s @SuperBuilder, y después compara el resaltado con y sin el builder personalizado. Rastrea el punto de entrada de análisis de sintaxis o de parsing de Java de la extensión Java de VSCode; se considera terminado cuando la estructura de la clase y los colores de las clases sigan renderizándose correctamente en ambos casos.