Skip to content

[BUGFIX] Centralize Lombok version management to resolve compilation issues - #299

Open
ZenithDev1 wants to merge 1 commit into
xkcoding:masterfrom
ZenithDev1:fix/lombok-version-management
Open

ZenithDev1 wants to merge 1 commit into
xkcoding:masterfrom
ZenithDev1:fix/lombok-version-management

Conversation

@ZenithDev1

Copy link
Copy Markdown

Summary

This PR centralizes Lombok dependency version management in the root pom.xml to ensure consistent Lombok versions across demo modules.

Problem

The project imports Spring Boot 2.1.0.RELEASE dependency management, which resolves Lombok to an older version (1.18.2) in the tested module.

This older Lombok version causes compilation compatibility issues when building the project with newer JDK versions.

Changes

  • Added Lombok to the root ''dependencyManagement'' section.
  • Set the centrally managed Lombok version to 1.18.30.
  • Kept individual module dependency declarations unchanged.
  • Preserved existing ''@requiredargsconstructor(onConstructor_ = @Autowired)'' usage.

Verification

Verified using Java 21.0.7 and Maven 3.9.10:

  • Confirmed the original dependency resolution used Lombok 1.18.2.
  • Confirmed Lombok 1.18.30 is resolved through the effective POM.
  • Verified the demo-dynamic-datasource module compiles with the existing annotation.
  • Executed a full repository build using mvn clean compile.
  • Result: BUILD SUCCESS across all Maven reactor modules.

Related Issue

Closes #285

感谢维护这个开源项目!希望这个改进能帮助项目更稳定地构建。谢谢!

@guxiren

guxiren commented Nov 11, 2026 via email

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]

2 participants