It means that even if your Java project doesn't directly use log4j as a dependency, nor mention it explicitly, it will be very likely included as a transitive dependency via other libs (and even logging frameworks!) that you use.

Even if your code doesn't directly use Log4j, it's exceedingly likely that a library you use, or a library that uses does.

They didn't get my original statement because I'm a PHP dev (no compiling involved)... sigh

That being said, I do rely on containers, micro services, and other tools like Jenkins that will need eval.

Even if you don't use l4j in your project, you are likely to use something that uses it; a transient dependency.