-
Bug
-
Resolution: Done
-
Major
-
7.27.0.Final
-
2019 Week 41-43 (from Okt 7)
-
3
-
-
Workaround Exists
-
- Define the versions of the dependent kjar projects in the respective pom itself instead of relying on a bom
-
NEW
-
NEW
When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom:
Running test with rules version 7.27.0.Final and -DgenerateModel=NO 13:01:05,903 [ERROR] Unable to build KieBase, could not find include: subkbase 13:01:05,908 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.27.0.Final:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.27.0.Final:build failed: Unable to get KieModule, Errors Existed: Error Messages: 13:01:05,910 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 13:01:05,911 [ERROR] text=Unable to build KieBase, could not find include: subkbase]
Note that such a build is successful with RHDM 7.3.1 if the executable model is not used (see reproducer).
- clones
-
RHDM-1107 kie-maven-plugin fails with nested kbases and dependency versions declared in bom
- Closed