This message was deleted.

Run a build scan, it will show why a dependency is pulled in.

…or, without a buid scan: • janino should appear elsewhere in the output • you could also use the

dependencyInsight

task Documentation: https://docs.gradle.org/current/userguide/viewing_debugging_dependencies.html#sec:identifying_reason_dependency_selection

well the build scan isn't helpful in my eyes either

Can you provide that build scan?

sure https://scans.gradle.com/s/moc7dyewvsjws

Maybe the spring dependency management plugin?

Yeah, was about to suggest the same. Also does

./gradlew dependencyInsight --dependency org.codehaus.janino:janino --configuration compileClasspath

bring and additionaly information? I fear not though, as the build scan is also surprisingly useless here.

sigh @Thomas Broyer was right. we recently switched to quarkus and there was still the spring plugin in place. thank you!

And the spring dependency management plugin hides the information

i will keep this in mind, thank you :)