Managing library versions declared through a bom from Spring boot but not from Girders #31
Description
When using the dependencies through an import of girders-platform-bom we get the Spring dependencies through the import of spring-boot-dependencies. The spring boot bom manages the version for certain libraries (e.g. netty) through properties.
With this setup forcing an update of the version does not work. Redefining the version property has no effect. What should be done is to declare the respective bom for the library with the correct version before the declaration of spring-boot-dependencies, which is something that cannot be achieved in a consuming project as it is missing in the girders-platform-bom.
See https://stackoverflow.com/questions/74872327/updating-library-version-but-transitive-dependenies-stay-the-same for more details.
Possible approaches that I can think of:
- Declare all the boms also on the Girders level so that they can be overriden
- Introduce a mechanism that allows the managing of the version
- Find a way to exclude certain aspects, so that they have to be managed explicitly in the consuming project