[KARAF-4306] karaf-maven-plugin is not assembling the correct version of dependencies

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 4.0.4
• Component/s: karaf
• Assignee: Jean-Baptiste Onofré
• Reporter: Raman Gupta
• Created: 03/Feb/16 00:57
• Updated: 16/Sep/18 04:35
• Resolved: 15/Dec/17 09:33

Description

This is similar to KARAF-3994.

I see that the commit for that issue added the following TODO:

• TODO Need to also check for version ranges. Currently ranges are ignored and all features matching the name

I have a similar problem – the generated system repo contains all versions of a feature that is matched by a range, not just the highest one that fulfills all of the requirements of the boot features. This is an issue because the generated repo may contain older (or newer) versions of libraries that have CVEs against them, which is then flagged by ops.

For example:

My feature depends on spring-dm which depends on spring range [2.5.6,4). At runtime, Karaf only needs and uses Spring 3.2.14, but my system repo contains Spring 3.1.4 (as well as three versions of Spring 4), all of which are defined in the Karaf Spring repo. And of course, Spring 3.1.4 has CVEs against it, so the system is flagged by ops as using jars with security problems (even though those jars are not actually used by the app).

Shouldn't the Builder apply the same resolution logic as is used by Karaf itself, and assemble only those jars?

Issue Links

• relates to: KARAF-3994 karaf-maven-plugin is ignoring the feature version and installing all available versions of given feature in the repository.
• relates to: KARAF-4712 Karaf assembly builder does not handle versions correctly