anchor.diff:  - a Java lambda was used to implement the class,
   - or the class has been loaded by a classloader unknown to Gradle.
   
  -From Java code, it is quite easy to accidentally use a Lambda to implement a task action.
  +Using a Java lambda means that the bytecode uses invoke-dynamic instead of creating an actual sub-class.
  +The class for the invoke-dynamic instruction is generated at JVM runtime and Gradle cannot uniquely identify this class across different JVMs.
  +From Java code, it is quite easy to accidentally use a lambda to implement a task action.
   
   ```java
   tasks.register("myTask",
  
positive.code: );
  ```
  
  For the second case, instead of loading your class by a classloader unknown to Gradle, you can use Gradle's built-in ways to load the class.
  For example, the <<worker_api.adoc#,worker API>> allows using a different classloader.
  
negative.code: );
  ```
  
  Gradle isn't able to track the implementation of this task action.
  What you can do instead is to use an anonymous inner class.
  
  ```java
  