Skip to content

feat(build): dual Spring Boot profile support & local one-click dual-version verify#3

Merged
lk-keep-fighting merged 2 commits into
mainfrom
feat-dual-profiles-local-scripts-verify-two-versions
Nov 24, 2025
Merged

feat(build): dual Spring Boot profile support & local one-click dual-version verify#3
lk-keep-fighting merged 2 commits into
mainfrom
feat-dual-profiles-local-scripts-verify-two-versions

Conversation

@cto-new

@cto-new cto-new Bot commented Nov 11, 2025

Copy link
Copy Markdown
Contributor

Summary

This PR introduces support for verifying compatibility with both Spring Boot 2.7.x and 3.2.x via Maven profiles and a local script, allowing developers to validate both versions with a single command prior to automated CI/CD rollout.

Details

  • Added spring-boot-2 (default) and spring-boot-3 Maven profiles at root, enabling central control of BOM version selection.
  • Refactored module pom.xmls (logic-ide, logic-sdk, test-suite) to defer to the selected BOM for Spring Boot version resolution.
  • Implemented scripts/verify-compatibility.sh as a one-click tool to sequentially build/test logic-ide and dependencies under both profiles for local assurance.
  • Updated README and automation design documentation to include local dual-profile verification and usage instructions.

Warning: Task VM test is not passing, cto.new will perform much better if you fix the setup

cto-new Bot and others added 2 commits November 11, 2025 08:02
…lick script

Enable project-wide verification against both Spring Boot 2 and 3.2.x
using new Maven profiles and a local helper script to improve
compatibility assurance prior to automation pipeline implementation.

- Introduce `spring-boot-2` (default) and `spring-boot-3` profiles in the
  parent pom to centralize Spring Boot BOM version control
- Remove hardcoded boot version coordinates from logic-ide, logic-sdk,
  test-suite modules for inheritance from BOM
- Add scripts/verify-compatibility.sh for sequential dual-profile
  validation via mvnw
- Update documentation in README and test/release design to guide usage

Developers can now validate both dependency stacks locally with a single command, facilitating cross-version assurance in the early stage of automation rollout.
@lk-keep-fighting lk-keep-fighting merged commit a8d09e3 into main Nov 24, 2025
0 of 3 checks passed
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.

1 participant