关于IntelliJ中Lombok Jar内非注解文件以.SCL.lombok结尾的原因及处理方式咨询

Great question! Let me break this down for you in plain terms—this is one of those behind-the-scenes details most developers don’t notice until they dig into Lombok’s internals.

First, let’s decode the acronym: SCL stands for Shadow Class Library. That suffix is a marker added by IntelliJ’s Lombok plugin to distinguish "shadow copies" of Lombok’s internal classes from its public annotation classes.

Here’s the core logic:
Lombok’s JAR has two distinct types of classes:

1. Public annotation classes (like @Getter, @Setter, @Accessors): These are meant to be used directly in your code, so they’re stored as standard Java class files in the JAR and show up normally in IntelliJ.
2. Internal processor classes (like HandleAccessors): These are Lombok’s workhorses—they handle parsing annotations, generating bytecode, and all the magic that makes Lombok work. They’re not meant to be referenced by your code, and the plugin needs to isolate them to avoid conflicts and enable special handling.

The .SCL.lombok suffix tells IntelliJ: "Hey, this is a shadowed copy of a Lombok internal class, managed exclusively by the Lombok plugin."

Let’s walk through how this works step by step:

• Step 1: Plugin Scans the Lombok JAR
  When you open a project with Lombok in IntelliJ, the Lombok plugin scans the JAR to separate public annotations from internal processor classes.
• Step 2: Shadow Copy Creation
  For internal processor classes, the plugin creates an in-memory "shadow copy" of the class. This copy matches the original code exactly, but gets the .SCL.lombok suffix attached to its filename.
• Step 3: Isolated Class Loading
  These shadowed classes are loaded using a custom class loader owned by the Lombok plugin, not IntelliJ’s default system class loader. This prevents any conflicts with other classes in your project or other plugins.
• Step 4: IDE Display & Usage
  When you navigate to one of these internal classes in IntelliJ, you’re actually viewing the shadow copy (hence the suffix). The plugin uses these shadowed classes to power features like code completion, refactoring support, and real-time previews of Lombok-generated code.

A quick side note: These .SCL.lombok files don’t exist physically in the Lombok JAR—they’re virtual files generated by the plugin in memory to let you inspect Lombok’s internal logic without messing with the original JAR’s compiled code.

内容的提问来源于stack exchange，提问作者aminbhst