thanks for your response. I can describe what I was observing but I am not sure I'll be able to provide the necessary details to conclude where the info gets lost.
In our case we are scanning the classpath looking for methods with specific annotations and then we are trying to figure out the method parameter names (among other things) using the Jandex library . It appears Jandex does not actually require classes to be compiled with the `-parameters` argument to figure it out, it may pull the info from the local var table instead, IIUC.
So, we have a Quarkus JaCoCo extension that allows to integrate JaCoCo into Quarkus tests. The extension calls the JaCoCo instrumenter API here . If instead of returning the `enhanced` byte array I return the original `bytes` array, Jandex can figure out the method parameter names. I we return the `enhanced` array, Jandex fails to figure it out. If we compile the classes with the `-parameters` argument though, it works.
I realize we need to debug this further to provide more info for you about what exactly Jandex is looking for in this case. But I thought I would still report the issue just in case it rings a bell.