This is unfortunate as I basically do not know (or care) which version of Geolatte I'm using, I let Hibernate Spatial decide that for me. (its version is in turn decided by Spring Boot's BOM). Keeping these version numbers in lock-step is a hazzle.
Not sure what is the best practice solution here but I think the solution is if Geolatte project would publish a BOM and then have the Hibernate Spatial project consume the BOM in its <dependencyManagement> section.
I'm using Geolatte via Hibernate Spatial. All wrapped up in a standard Spring Boot 3.x application.
When I pull in the Geolatte JSON module I need to explicitly specify the version:
rather than simply:
This is unfortunate as I basically do not know (or care) which version of Geolatte I'm using, I let Hibernate Spatial decide that for me. (its version is in turn decided by Spring Boot's BOM). Keeping these version numbers in lock-step is a hazzle.
Not sure what is the best practice solution here but I think the solution is if Geolatte project would publish a BOM and then have the Hibernate Spatial project consume the BOM in its
<dependencyManagement>
section.