fix(pom): re-enable -parameters compiler flag

[herbie-bot]

Problem

Commit d43152f ("remove unused maven plugins from pom.xml to streamline build configuration") removed the maven-compiler-plugin configuration:

<configuration>
    <parameters>true</parameters>
</configuration>

on the assumption it was unused. It is not unused. Spring relies on formal parameter names being present in the bytecode (-parameters) to:

• resolve constructor/method injection by name — including disambiguating two beans of the same type by the parameter name,
• bind @RequestParam / @PathVariable without an explicit name,
• perform @ConfigurationProperties constructor binding.

Spring Boot's own spring-boot-starter-parent enables -parameters by default for exactly this reason.

Impact

After bumping spring-services to parent 1.2.0, the whole spring-services-core test suite failed at ApplicationContext load (103 errors):

NoUniqueBeanDefinitionException: No qualifying bean of type
'…JsonAuthenticationEntryPoint' available: expected single matching bean
but found 2: jwtAuthenticationEntryPoint, apiKeyAuthenticationEntryPoint

Two beans of the same type could no longer be told apart, because Spring's by-name fallback needs the parameter names that -parameters preserves.

Fix

Re-add the flag as the maven.compiler.parameters property (honored by maven-compiler-plugin 3.15.0), consistent with how maven.compiler.source / maven.compiler.target are declared.

Verification

Built spring-services against this patched parent (1.3.0-SNAPSHOT): the previously-failing module now passes — 294 tests, 0 errors, BUILD SUCCESS.

Note: the same removal commit also dropped a maven-surefire-plugin --add-opens argLine. That is unrelated to this failure and is intentionally not restored here.

🤖 Generated with Claude Code