-
Bug
-
Resolution: Done
-
Major
-
7.4.1.GA
-
1
-
-
-
-
-
-
CR1
-
+
-
Workaround Exists
-
- Define the versions of the dependent kjar projects in the respective pom itself instead of relying on a bom
-
-
2019 Week 41-43 (from Okt 7)
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.23.0.Final-redhat-00003 and -DgenerateModel=NO 12:41:58,315 [ERROR] Unable to build KieBase, could not find include: subkbase 12:41:58,320 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build failed: Unable to get KieModule, Errors Existed: Error Messages: 12:41:58,323 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 12:41:58,324 [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).
- is cloned by
-
DROOLS-4602 kie-maven-plugin fails with nested kbases and dependency versions declared in bom
- Closed