Red Hat Bugzilla – Bug 1108070
kie-maven-plugin throws error when kmodule including kbase
Last modified: 2014-08-06 15:53:23 EDT
Created attachment 907615 [details] kiebase-inclusion-6.0.1.7z Description of problem: An error is experiencied by building a project that contains a kmodule.xml which uses an include such as: <kbase name="kbase2" includes="kbase1"> When generating a kjar there is an error indicating the included kbase could not be found: [ERROR] Message [id=1, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 text=Unable to build KieBase, could not find include: kbase1] If using brms version 6.0.2-SNAPSHOT the build succeeds but with the release version 6.0.2-redhat-6 it fails. Version-Release number of selected component (if applicable): BRMS 6.0.1 How reproducible: Always Steps to Reproduce: 1. Download attached files (named-kiesession-6.0.1.7z and kiebase-inclusion-6.0.1.7z); 2. unzip and 'mvn install' named-kiesession-6.0.1 project. It should be built successfully. 3. unzip and 'mvn install' kiebase-inclusion-6.0.1 project. It will throw the error above. Actual results: [ERROR] Message [id=1, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 text=Unable to build KieBase, could not find include: kbase1] Expected results: It should build succesfully. Additional info:
Created attachment 907616 [details] named-kiesession-6.0.1.7z
> By 6.0.2-SNAPSHOT, does he mean community? Or a build out of the product branch? Where is he getting that from? 6.0.2-SNAPSHOT is referred to in the source code distributed by Red Hat in jboss-bpms-brms-6.0.0.GA-redhat-2-source.zip.
Amana, sorry, but still confused by this: > 6.0.2-SNAPSHOT is referred to in the source code distributed by Red Hat in jboss-bpms-brms-6.0.0.GA-redhat-2-source.zip. You mean that this test fails with the product binaries, but work if building the product source code and using it? Can you please clarify? Mario, can you please check if you are able to reproduce it using our current 6.0.x branch?
The implementation of this use case was totally missing, so I don't see how it could have ever worked. Fixed by https://github.com/droolsjbpm/drools/commit/7320e0cfd
Cherry-picked to 6.1.x branch with https://github.com/droolsjbpm/drools/commit/d1f267f5e
Cherry-picked to 6.0.x branch with https://github.com/droolsjbpm/drools/commit/9fa4169c6
I used the attached project and reproduced the problem with 6.0.3-redhat-2 dependencies (6.0.2.ER3) and verified it is fixed with 6.0.3-redhat-3 (6.0.2.CR1) dependencies. Interestingly, I couldn't reproduce in Business Central 6.0.2.ER3.