# Lombok - Remove this unused "name" private field. (java:S1068)

**URL:** <https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993>\
**Category:** SonarQube Server / Community Build\
**Created:** [December 17, 2025, 9:45am UTC](https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993 "2025-12-17T09:45:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_CHABI](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sam_chabi/32/66296_2.png) [@Sam\_CHABI](https://community.sonarsource.com/u/Sam_CHABI)\
**Post date:** [December 17, 2025, 9:45am UTC](https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993/1 "2025-12-17T09:45:23Z")

</div>

Hi,

We’re using **SonarQube 2025.1 LTA** to analyze a Java project that uses **Lombok**. Our project is on **Java 21** , and we run the analysis using the **SonarQube Scanner CLI**.

SonarQube is reporting the issue **“Remove this unused ‘name’ private field”** in a class annotated with Lombok annotations (the field is actually being used through Lombok’s generated methods).

Here’s an example of the class causing the issue:

java

```auto
import lombok.AllArgsConstructor;
import lombok.Data;
import lombok.NoArgsConstructor;

@Data
@NoArgsConstructor
@AllArgsConstructor
public class Project {
    private String name;
}

```

Are there any configurations we might be missing to properly handle Lombok-annotated fields?

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [December 17, 2025, 3:05pm UTC](https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993/2 "2025-12-17T15:05:26Z")

</div>

Hi,

What version of SonarQube are you using? This one looks relevant, and it was resolved in April:

> [SONARJAVA-4933](https://sonarsource.atlassian.net/browse/SONARJAVA-4933) FP on S1068 with lombok @Data, @Getter, @Setter annotations

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![Sam\_CHABI](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sam_chabi/32/66296_2.png) [@Sam\_CHABI](https://community.sonarsource.com/u/Sam_CHABI)\
**Post date:** [December 17, 2025, 3:28pm UTC](https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993/3 "2025-12-17T15:28:48Z")

</div>

> [@ganncamp](#):
>
> his one looks relevant, and it was resolved in

we are using SonarQube v2025.1.3

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [December 17, 2025, 3:49pm UTC](https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993/4 "2025-12-17T15:49:07Z")

</div>

Hi,

So you don’t have that fix. Once you upgrade, this should go away. In the meantime, your best bet is to mark the issue a False Positive.

&nbsp;  
HTH,  
Ann

---

<div class="post-metadata">

**Author:** ![Sam\_CHABI](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sam_chabi/32/66296_2.png) [@Sam\_CHABI](https://community.sonarsource.com/u/Sam_CHABI)\
**Post date:** [December 17, 2025, 4:30pm UTC](https://community.sonarsource.com/t/lombok-remove-this-unused-name-private-field-java-s1068/153993/5 "2025-12-17T16:30:04Z")

</div>

> [@ganncamp](#):
>
> 1068

Thanks you for your reply