From 87e8af476a40b9a7b1c53a82a0fd1d8ba1ead707 Mon Sep 17 00:00:00 2001
From: Reinier Zwitserloot <r.zwitserloot@projectlombok.org>
Date: Thu, 7 Aug 2025 02:02:02 +0200
Subject: [PATCH] [comment] Added explanation: We skip ecj check on
 `NonNullOnRecordExistingConstructorz`.

---
 .../resource/after-ecj/NonNullOnRecordExistingConstructor.java  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/transform/resource/after-ecj/NonNullOnRecordExistingConstructor.java b/test/transform/resource/after-ecj/NonNullOnRecordExistingConstructor.java
index c16d347e..75be79fb 100644
--- a/test/transform/resource/after-ecj/NonNullOnRecordExistingConstructor.java
+++ b/test/transform/resource/after-ecj/NonNullOnRecordExistingConstructor.java
@@ -1,5 +1,5 @@
 // version 14:
-// skip compare content
+// skip compare content: At time of writing, the `@NonNull` annotation causes our handler to produce an explicit-params constructor (i.e. `public NNOREC(String a) {` instead of `public NNOREC {`) with `@NonNull`, and in the statements the null check. But (?) other eclipse versions might not, hence, we ignore content.
 import lombok.NonNull;
 public record NonNullOnRecordExistingConstructor(String a) {
   public NonNullOnRecordExistingConstructor {