Let modules reuse to Kauri's version of a dependency.

[bruno]

To make it easier to upgrade towards newer Kauri versions, or to run on multiple Kauri versions, it would be helpful if own modules would not list explicit version numbers for dependencies which are also Kauri dependencies.

Common examples of such dependencies include Spring, JAX-RS api, Restlet api, ...

This should both be the case at build-time and run-time.

Solution: still to be researched. Probably some properties file listing these versions, which can be passed to Maven and is build into the Kauri Runtime.

[bruno]

Some first research and thoughts:

• Maven doesn't support any other properties than those listed in the <properties> element or passed using -D. Specifying an external property file is not possible.

• the artifact-versions-list should be available to:
  • the Kauri Runtime, for resolving (at runtime) the version to use
  • the genclassloader plugin: to know it should not add the versions for those artifacts when generating the classloader.xml
  • archetype: to include that set of properties in the <properties> section of the generated pom (or other solution to use those properties at build time)

Will not work further on this for the moment.

[bruno]

From offline comments I received:

• there appears to be some ability to refer to depenencies listend in other poms
• might approach it by creating a dummy dependency listing pom (though would then force user to use all these dependencies)

[mpo]

please check if this is still relevant and close or move over to beyond 0.4

[mpo]

beyond 0.4 scope