[BUG] Lombok stop working on Eclipse 4.18.0

[danibs]

Describe the bug
Annotation @Data doesn't create fluent setter.

To Reproduce

@Data
public class ResultBean {
	private String id;
	private String code;
}

final ResultBean r1 = new ResultBean().setId( "1" ).setCode( "c1" );
  --> _Cannot invoke setCode(String) on the primitive type void_

Version info (please complete the following information):

• Lombok version: 1.18.26
• Eclipse Version: 4.18.0.RELEASE ( Spring Tool Suite 4 ) - Build Id: 202303131455
• S.O. Ubuntu 18.04
• Java 17

[dstango]

I think you mixed up versions here: Spring Tools 4.18.0 is based on Eclipse 2023-03 (aka Eclipse 4.27).

Anyhow: your error seems to be related to #3332, as the error message indicates that your lombok.config might contain lombok.accessors.fluent = true (see https://projectlombok.org/features/experimental/Accessors).

[danibs]

In my case the property is lombok.accessors.chain = true but yes, I think you catch the real problem!

[dstango]

yes, I picked the wrong config option, sorry :-)

[luca-bassoricci]

also lombok.log.fieldName stops to work after Eclipse upgrade

Eclipse IDE for Java Developers (includes Incubating components)

Version: 2023-03 (4.27.0)
Build id: 20230309-1520
(c) Copyright Eclipse contributors and others 2000, 2023. All rights reserved. Eclipse and the Eclipse logo are trademarks of the Eclipse Foundation, Inc., https://www.eclipse.org/. The Eclipse logo cannot be altered without Eclipses permission. Eclipse logos are provided for use under the Eclipse logo and trademark guidelines, https://www.eclipse.org/logotm/. Oracle and Java are trademarks or registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

This product includes software developed by other open source projects including the Apache Software Foundation, https://www.apache.org/.

Lombok v1.18.26 "Envious Ferret" is installed. https://projectlombok.org/

[dstango]

also lombok.log.fieldName stops to work after Eclipse upgrade

All this seems to be a result of #3332, so I'd guess these issues all to be duplicates of #3332.

[Rawi01]

#3332 is fixed and there will be a release soon