Description of problem:

KIE-CI does not parse kjar's dependencies if their version is not declared in the pom.xml (it is declared in the parent pom's <dependencyManagement>). KIE-CI also does not evaluate any properties in the pom, so specifying kjar's dependency version as ${project.version} does not work.

This is visible mainly in OSGi environment, because the kjar's dependencies are not available on the classpath.

There is an obvious workaround to specify explicitely the dependency version, but this approach is not maintainable well in larger projects.

Version-Release number of selected component (if applicable):
BRMS 6.2.1

How reproducible:
always

Steps to Reproduce:
1. prepare a kjar which declares a dependency on another jar, eg. with domain model classes, but the dependency version is inherited from parent pom's <dependencyManagement>

2. try to build the kjar

I am going to provide a better reproducer later (a test not tight to OSGi).

Actual results:
KieModule is built, but the rules fail to compile because of missing classes from the dependency (KieContainer creation does not fail, but the rules are not available - they do not fire).

Expected results:
KieModule is built successfully.