[BUG] @JsonUnwrapped not copied to @Builder methods in Eclipse IDE for record

[MathiasDamMC]

Describe the bug
In Eclipes IDE lombok fails to copy the Jackson annotation @JsonUnwrapped from a record to the method on @builder's. This works fine outside of Eclipse IDE. This issue seems related to #2736

Notice, this seems to work fine if used with class rather than record

To Reproduce
Run the following test case, this will fail in Eclipse as the @JsonUnwrapped is not copied to the builder() class method inner(). The same test case will work outside of Eclipse.

package test;

import static org.assertj.core.api.Assertions.assertThat;

import org.junit.jupiter.api.Test;

import com.fasterxml.jackson.annotation.JsonUnwrapped;

import java.util.Arrays;

import lombok.Builder;
import lombok.extern.jackson.Jacksonized;

class RecordAnnotationsNotCopiedTest {
    @Builder
    @Jacksonized
    record Example(@JsonUnwrapped Inner inner) {}
    
    record Inner(String s) {}
    
    @Test
    void testLombok() throws NoSuchMethodException, SecurityException {
        var method = Arrays.asList(Example.builder().getClass().getMethods()).stream().filter(m -> m.getName().equals("inner")).findFirst().get();
        assertThat(method.getAnnotations().length).isEqualTo(1);

    }
}

Expected behavior
This should also work in Eclipse IDE.

Version info (please complete the following information):

• Lombok v1.18.24
• Platform Eclipse Version: 2022-06 (4.24.0)

[Rawi01]

This issue affects all copyable annotations on record components and is not limited to @Jacksonized or @JsonUnwrapped.

[namannigam]

@rzwitserloot @Rawi01 After this change, the intent was to also imply this over classes(not only records)?
Asking since, we figured this out the hard way, where the upgrade to Lombok 1.18.30 resulted in a few test setup failures in our application.

@lombok.Builder
@lombok.Getter
class CustomResponse implements Serializable {
    @jakarta.annotation.Nonnull
     private String [] messages;

     @jakarta.annotation.Nonnull
     private String status;
}

in our test case, we were able to mock this earlier as

CustomResponse.builder().messages(new String[]{"mock"}).build();

Of course, I acknowledge that the test case should have taken into consideration to mock CustomResponse with status.
But this piece of code doesn't work now. The signs are good but hoping that it implies across and we won't have to make changes back and forth.

[rzwitserloot]

@namannigam I'm not quite sure what, specifically, is failing. How does @Json relate to your snippet in any way? I'm not all that familiar with serialization or mocking, so you're going to have to spell out exactly -stick this in a source file, compile it like this, using these libraries and tools (e.g. Jsonthisorthat).

Or, if it's solely about the fact that your CustomResponse.builder().messages(new String[]{"mock"}).build(); used to work but no longer does, explain exactly how that mock thing works. Why does it fail now? Include the exception, for example. Right now I need to spend 5 hours to try to reconstruct what you're doing before I can be sure I'm fixing the problem.

[namannigam]

The difference is in the auto generated .class file where the latest version 1.18.30 takes annotations like @Nonnull into considerations and throws NullpointerException while with previous version this wasn't the case. If you stil need a reproducible example, let me know and I would share that as soon as I get some time off work.

[Rawi01]

@namannigam I think you skipped 1.18.28 because we added support for jakarta.annotation.Nonnull in this release. That is unrelated to annotations on record components.

Changelog:

FEATURE: Jakarta has some non-null annotations (such as jakarta.annotation.Nonnull) which we now support. Issue #3346.

[namannigam]

@Rawi01 Got it, that should resolve my concern. My bad for not specifying that I was relying on the version upgrade of Lombok via spring-boot.