Create a release train for migration to SpringBoot 3.x

[openwms]

Currently all the services use a version 2.7.x

Resolving configuration from the Spring Cloud Config server at runtime is not that easy anymore since it requires the use of legacy support org.springframework.cloud:spring-cloud-starter-bootstrap in latest releases. The thing is that OpenWMS.org uses the Service Registry First approach https://github.com/openwms/org.openwms/wiki/Secured-Eureka-First-services-on-Heroku#eureka-first-bootstrap. Only basic configuration is obtained at compile-time and all other required configuration is fetched at runtime. This is an issue for pre-compiled and pre-linked executables, because all runtime config must exist at build-time.

[cloorc]

Hi @openwms , thanks for your excellent ideas on WMS, could you please tell me how can I build a monolith application? BTW, wiki (https://wiki.butan092.startdedicated.de/projects/openwms/wiki) seems not work now.

[openwms]

Hi @cloorc . Thank you for your interest. Have a look at Spring profiles. Some services use Spring profiles for kinda "feature toggling". Running them with profile DISTRIBUTED means in a microservice architecture. Bundling them into a WAR and running the whole application not DISTRIBUTED and STANDALONE means monolithic and all-in-one. Regarding the wiki link, thanks for the reminder, I've to rebuild all pages in wiki