As pointed out in https://github.com/spring-projects/spring-framework/issues/29612#issuecomment-1463715442, ParameterNameDiscoverer is used even when parameter name resolution is not needed and could be skipped via a proper ConstructorArgumentValues#containsNamedArgument.
That could be beneficial both from an efficiency and compatibility perspective (no need to use -parameter javac option for such use case).
Comment From: moritzreiter
I came here through the precursor issue (#29612). I get the same warning described there in a Spring Boot project in the context of using the Pebble Templates Engine:
2023-04-12T15:56:46.198+02:00 WARN 25044 --- [ restartedMain] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: io.pebbletemplates.boot.autoconfigure.PebbleAutoConfiguration
After reading the comments there and this issue here I was hoping it would get fixed by upgrading to Spring 6.0.7, but it doesn't.
Or is it maybe a legitimate warning in this case so that I should file an issue over at the Pebble repo?
Comment From: vishalsingh2972
Getting similar warning after trying everything....any resolution?
Apr 14, 2023 1:09:54 AM org.springframework.core.LocalVariableTableParameterNameDiscoverer inspectClass
WARNING: Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: demo.LoggingAspect
I am currently using Spring 6.0.7