Description
With dependency management we resolved some misalignments. Anyway, on every update, we need to keep aligned several dependencies and this is sometimes very annoying.
We may follow 2 possible ways to improve this:
- We should try to use
<type>pom</type> dependency in mapstore, directly from the main geostore's (and http proxy) dependency, to inherit all dependencies and avoid to copy several versions across projects, reducing the error possibilities.
- Enforce with automation checks that prevents versions to be misaligned
I'd suggest the first solution, because is more canonic and uses maven native dependency resolution system, rather than a custom automatic solution made by us.
What kind of improvement you want to add? (check one with "x", remove the others)
Description
With dependency management we resolved some misalignments. Anyway, on every update, we need to keep aligned several dependencies and this is sometimes very annoying.
We may follow 2 possible ways to improve this:
<type>pom</type>dependency in mapstore, directly from the main geostore's (and http proxy) dependency, to inherit all dependencies and avoid to copy several versions across projects, reducing the error possibilities.I'd suggest the first solution, because is more canonic and uses maven native dependency resolution system, rather than a custom automatic solution made by us.
What kind of improvement you want to add? (check one with "x", remove the others)