From 887479d05612248146997dec6d1b2118ccab7ee9 Mon Sep 17 00:00:00 2001 From: Hendrik Ebbers Date: Thu, 16 Jul 2026 18:13:44 +0200 Subject: [PATCH] fix(pom): re-enable -parameters compiler flag MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Commit d43152f ("remove unused maven plugins") dropped the maven-compiler-plugin true configuration, assuming it was unused. It is not: Spring relies on formal parameter names being present in the bytecode to resolve constructor/method injection by name — e.g. to disambiguate two beans of the same type by the parameter name, and to bind @RequestParam/@PathVariable/@ConfigurationProperties without an explicit name. Spring Boot's own parent enables -parameters by default for exactly this reason. Without the flag, downstream Spring projects fail at ApplicationContext load with NoUniqueBeanDefinitionException (observed in spring-services after bumping to parent 1.2.0: two JsonAuthenticationEntryPoint beans could no longer be told apart). Re-added as the maven.compiler.parameters property (honored by maven-compiler-plugin 3.15.0), consistent with how maven.compiler.source/target are declared. Co-Authored-By: Claude Opus 4.8 (1M context) --- pom.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/pom.xml b/pom.xml index 9feffe4..5c0e44f 100644 --- a/pom.xml +++ b/pom.xml @@ -39,6 +39,11 @@ 21 21 + + true