#1525: Document known issue and workaround for lombok plugin in Eclipse

[Paras14]

This PR fixes #1525

Implemented changes:

• Added a Problem, Workaround and Status section to the eclipse chapter of lombok.adoc
  describing that the lombok plugin for eclipse installs successfully but never activates.
• Documented the root cause (lombok has to be loaded as Java agent via -javaagent, which an
  eclipse plugin installed into a running eclipse cannot do) and linked the upstream issue
  [BUG] Eclipse plugin not working but manually adding javaagent to eclipse.ini works projectlombok/lombok#3621.
• Documented the manual workaround via eclipse.ini including the side effects
  (shared across all IDEasy projects using the same eclipse version, lost on eclipse update).
• Documented in the Status section why we deliberately do not automate this in IDEasy,
  so the discussion does not have to be repeated in the future.
• Added the issue to CHANGELOG.adoc.

This is a documentation-only change, no code was touched.

---

Testing instructions

Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:

1. Review the rendered documentation of documentation/lombok.adoc (section Lombok in Eclipse).

2. To verify the documented workaround, create a small maven project in $IDE_HOME/workspaces/main with this pom.xml:

   <project xmlns="http://maven.apache.org/POM/4.0.0"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
     <modelVersion>4.0.0</modelVersion>
     <groupId>com.example</groupId>
     <artifactId>lombok-test</artifactId>
     <version>1.0-SNAPSHOT</version>
     <properties>
       <maven.compiler.release>21</maven.compiler.release>
       <lombok.version>1.18.42</lombok.version>
     </properties>
     <dependencies>
       <dependency>
         <groupId>org.projectlombok</groupId>
         <artifactId>lombok</artifactId>
         <version>${lombok.version}</version>
         <scope>provided</scope>
       </dependency>
       <dependency>
         <groupId>org.slf4j</groupId>
         <artifactId>slf4j-api</artifactId>
         <version>2.0.16</version>
       </dependency>
     </dependencies>
     <build>
       <plugins>
         <plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-compiler-plugin</artifactId>
           <version>3.15.0</version>
           <configuration>
             <proc>full</proc>
             <annotationProcessorPaths>
               <path>
                 <groupId>org.projectlombok</groupId>
                 <artifactId>lombok</artifactId>
                 <version>${lombok.version}</version>
               </path>
             </annotationProcessorPaths>
           </configuration>
         </plugin>
       </plugins>
     </build>
   </project>

Add a class com.example.LombokTest annotated with @Slf4j that calls log.info("test") in main. E.g.:

package com.example;

import lombok.extern.slf4j.Slf4j;

@Slf4j
public class LombokTest {

public static void main(String[] args) {
 log.info("Lombok works!");
}
}

Note: lombok 1.18.40 or newer is required because IDEasy ships JDK 25, and annotation
processing has to be enabled explicitly via <proc>full</proc> since javac no longer runs
annotation processors by default as of JDK 23.

3. Run ide mvn clean compile, the build should succeed.

4. Import the project into eclipse via ide eclipse - eclipse reports log cannot be resolved
   even though the lombok plugin is listed under About Eclipse IDE > Installation Details.
   This is the reported problem.

5. Follow the documented workaround and add
   -javaagent:«absolute-path-to-lombok.jar» as last line of
   $IDE_HOME/software/eclipse/eclipse.ini.

6. Restart eclipse via ide eclipse, then run Maven > Update Project... on the project(Right click on the project directory> Maven>Update Project>check the directory>OK. The compile error should be gone.

[JoelAdbu]

Looks good to me. The description is clear and explains the current Lombok issue well.