modules job (ke-wb-distributions/kie-eap-integration) needs enhancement to enable the bpms and brms distribution generating in one build instead of two separate run.
Hi, In order to build all EAP modules distributions in a single build, the "kie-eap-integration" module has been splitted into several modules: - kie-eap-integration-core: Contains all builder core files. - kie-eap-integration-distributions: Contains all distributions to generate. - kie-eap-integration-bpms: Contains the generation of the BPMS distribution for modules. - kie-eap-integration-brms: Contains the generation of the BRMS distribution for modules. Now you can build all distribution using a single maven build. See https://github.com/droolsjbpm/kie-wb-distributions/blob/master/kie-eap-integration/README.md Other tasks done: ================= - Changed generated artifact names: - BPMS static layer -> eap-modules-distributions-X.Y.Z-bpms-layer.zip - BPMS webapp -> eap-modules-distributions-X.Y.Z-org.kie.kie-wb-webapp.war - BPMS jBPM dashboard -> eap-modules-distributions-X.Y.Z-SNAPSHOT-org.jbpm.dashboard.jbpm-dashboard.war - BRMS static layer -> eap-modules-distributions-X.Y.Z-brms-layer.zip - BRMS webapp -> eap-modules-distributions-X.Y.Z-org.kie.kie-drools-wb-webapp.war - Created maven deploy task: Allows to deploy the generated artifacts into a JBoss EAP installation. - Documentation -> Updated all README.md files. Commits - master ================ - https://github.com/droolsjbpm/kie-wb-distributions/commit/b1ba180a570a3c71e30a2b0cf4a8dd931f37780b - https://github.com/droolsjbpm/kie-wb-distributions/commit/da00238fb44701d815c5f88e9bda950a1fa50dc7 Commits - 6.0.X ================ - https://github.com/droolsjbpm/kie-wb-distributions/commit/163152e9e17a8b9d52e662a3ff22aa3e4dc7dc1c
Commits - 6.0.X ================ Fix parent versions to 6.0.0-SNAPSHOT: https://github.com/droolsjbpm/kie-wb-distributions/commit/f3f163106be1cd5535295d5a4f722d218c921984
Fixing parent for 6.0.X branch -> https://github.com/droolsjbpm/kie-wb-distributions/commit/3015db340369fbbaec0f435c63e16f44527120eb
This issue is rather internal, related to productization process. It doesn't have an impact on customers. Verified in ER5.