Red Hat Bugzilla – Bug 1265353
[PROD] (6.1.z) fuse-bxms-integration should include drools-karaf-feature.xml
Last modified: 2016-05-08 21:24:51 EDT
+++ This bug was initially created as a clone of Bug #1265199 +++
Description of problem:
GSS team has spot that the drools-karaf is missing in the fuse integration pack.
I think the drools karaf has been excluded for some reason in
Please have a look that if we need to include drools karaf and update the assembly.
I put this under BRMS team and assign to Kris for review since it's drools related.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Edson Tirelli on 2015-09-22 09:19:42 EDT ---
Mario, David, can you please comment on this? If it was excluded on purpose, can you please explain the reasons for it.
The drools/kie artifacts are not directly referenced in our features file. We use a range of versions. This is the main reason why it is not included neither drools nor switchyard artifacts.
Drools and Switchyard need to be installed previously in the environment where fuse-bxms-integ is going to be installed.
With this decision existing customer of drools can install fuse-bxms-integ without any problem.
See that drools-karaf-feature is not in fact a pure "drools artifact", it is a fuse feature file to make easier install the bundles on top of fuse.
The point is, Fuse customers does not install drools as every customers do, they need that file. The deliverable of BRMS packages include tons of other artifacts that fuse customers do not care, they only need the drools-karaf-feature and the karaf-feature from Integration Pack. It is not expect customers that would like to install Integration Package download any other additional package to consume only one xml file, drools-karaf-feature an karaf-features need to be delivered together, in the same zip file.
I understand the split of the features files like was done to allow BRMS engineers and Fuse engineers to work in each one individually, but the delivery should be done in the same Integration Pack archive. For that i do not know if a change in the assembly must be done or productisation should do any additional task.
It was split up that way so that one day we can have a fuse-integration bundles which does not need to be updated for each Fuse or BxMS release. As long as Fuse and BxMS stays compatible enough, updates of fuse or bxms should not require an update of the integration bundles. All that we should need to do is QE that the existing integration bundle works with the new bxms or fuse release.
After some talk with Hiram and as part of the comment above, we understand that the goal is to avoid in the future a new Integration Pack for each BxMS Pacth Update.
However as also described, customers should not download the full BxMS installation to get only the drools-karaf-feature. Also we can not keep it only in Maven Repo, the version there does not fit the brand product version and can confuse customers about which drools-karaf-feature version they should consume - it will also not be easy to get documented.
So, delivering it in a separated download can help with the problems above. Something intuitive like: Fuse Feature for BRMS and BPM Suite Engines 6.1 Update X ?
Ok, that sounds reasonable to me too.
I have upates our bxms product assembly to produce a separate zip package to include the drools-karaf feature xml.
The binary is availabe at:
Zip file on this address  contains the drools-karaf-features for BxMS 6.1.3. I consider this bug as verified for integration pack build intpkg-1.0.0.redhat-620147 (integration pack for BxMS 6.1.3).