STK parent pom's dependency mgmt section defines version as usual. Unfortunately it doesn't define all version there. Hence we have a mix of how version are defined.

e.g. dependency mgmt section defines versions for

• magnolia-module-activation, magnolia-module-data & junit
  but not for
• magnolia-core, magnolia-templating, magnolia-rendering, magnolia-ui-admincentral or commons-proxy & cglib-full

As most of these non-managed dependencies are used in several modules, updating any version e.g. when preparing a release is unnecessarily "complex"