Description of problem: Create distribution of BPMS/BRMS as a zip with all the modules and war files. Example of generated layered distribution ttps://docspace.corp.redhat.com/docs/DOC-153379 The scripts to produce this distribution from the previously generated wars have been delivered in https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/tree/master/script/jbossmodules This BZ is intended to keep track of any feedback, modifications and issues regarding this distribution.
I see that the current layout is shared for BRMS and BPMS. My original assumption was that there would be a BRMS module and the BPMS module would be referencing the BRMS one. (But maybe I was wrong in assuming that.)
From my understanding brms and bpms only are different in the webapp wars (different UF components), but the core modules are the same (both use jbpm, drools and kie). A similar distribution would be generated for BRMS, but using a different war as input (drools-wb instead of kie-wb).
(In reply to Pedro Zapata from comment #3) > From my understanding brms and bpms only are different in the webapp wars > (different UF components), but the core modules are the same (both use jbpm, > drools and kie). The issue here is that jBPM ships some binaries on top of Drools. If we ever need to update those, we will need to release a patch for both BRMS and BPMS, even though nothing would be touched inside BRMS. Is this the intended way? > A similar distribution would be generated for BRMS, but using a different > war as input (drools-wb instead of kie-wb). Sure, that makes sense.
JBoss Solder version with patch required. Pull request sent.
Hi. I had to create modules to support the openshift-origin-cartridge-jbpm-engine project : https://github.com/jbride/openshift-origin-cartridge-jbpm-engine Design goal for the cartridge was to make it fit in a small openshift gear. So the modules to support the jbpm-engine cartridge are as slim as possible.(currently 14 MB) and do not include most of the libraries found in the docspace page listed at the beginning of this BZ. Without derailing the existing work that's going on here related to this BZ (which i think is a great start), I'm wondering if Phase 2 of this BZ could be to allow for a little more extensibility. ie: 1) kie-core-modules.zip (kie-core, kie-common and dependencies) 2) jbpm-engine-modules.zip (jbpm engine modules with dependencies on kie modules) 3) cep-engine-modules.zip (cep modules with dependencies on kie modules) 4) biz-central-modules.zip (biz central modules with dependencies on kie, jbpm, etc) 5) etc .... jeff
A new version of the BPMS layer distribution zip have been uploaded to https://docspace.corp.redhat.com/docs/DOC-153379. This version contains new bpms layer modules: org.apache.batik org.apache.commons.httpclient org.apache.commons.digester org.apache.commons.fileupload org.apache.commons.jxpath org.apache.commons.logging org.apache.commons.validator com.opensymphony.quartz org.junit org.apache.xmlbeans
The latest veresion of the BPMS layer distribution zip have been uploaded to: https://docspace.corp.redhat.com/docs/DOC-153379. This BPMS version is currently stable, all services are available including REST. On next monday we will prepare the installation instructions and check BRMS with this jBPM layer JBoss EAP modules.
Hi, The DOCSPACE document for BPMS/BRMS EAP layer has been updated with new content and the last BPMS EAP layer distribution. See https://docspace.corp.redhat.com/docs/DOC-153379 The documentation for this distribution contains: - How to create the distribution - How to run the distribution into EAP - Some documentation for patches applied. This documentation can be found at: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/script/jbossmodules/README.md
The support for EAP 6.1.1 is already checked. For EAP 6.1.1 the CDI extensions bug is fixed, so they are no longer needed. The script prompts for a user input to decide where to put these extensions or not when running. The commit is https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/2dd6524f9e563dda24a2812fbcd8a080fd05cb4e
Hi, As the new bpms modules builder implementation (integrated with bpms maven application build) has been implemented at: "https://github.com/droolsjbpm/kie-wb-distributions/tree/master/kie-eap-integration", the old version (based on bash shell scripts) has been deleted from repository, see: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/4fc0ce2a88211f502860edce4223a0d7df452373
Due to the refactoring kie-commons to uberfire-commons, a new EAP static module for both BPMS/BRMS layers has been added: org.uberfire. Then some resource from org.kie module have been removed (as they no longer exists) and some resources have been added to org.uberfire module. Resources removed from org.kie module: org.kie.commons:kieora-commons-io:jar org.kie.commons:kie-nio2-api:jar org.kie.commons:kie-nio2-fs:jar org.kie.commons:kie-nio2-fs:jar org.kie.commons:kieora-api:jar org.kie.commons:kie-commons-cdi:jar org.kie.commons:kieora-backend-lucene:jar org.kie.commons:kie-commons-regex:jar org.kie.commons:kie-nio2-model:jar org.kie.commons:kie-commons-io:jar org.kie.commons:kie-commons-data:jar org.kie.commons:kie-commons-validation:jar org.kie.commons:kie-nio2-jgit:jar And the resources added to org.uberfire module are: org.uberfire:uberfire-io:jar org.uberfire:uberfire-commons:jar org.uberfire:uberfire-metadata-api:jar org.uberfire:uberfire-metadata-commons-io:jar org.uberfire:uberfire-nio2-model:jar org.uberfire:uberfire-nio2-api:jar org.uberfire:uberfire-nio2-fs:jar org.uberfire:uberfire-nio2-jgit:jar org.uberfire:uberfire-metadata-backend-lucene:jar
EAP 6.1.1 modules were added in ER5 distribution. Verified.