Bug 1029622
| Summary: | EAP Modules distribution - Review resources for org.jbpm static module | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Roger Martínez <romartin> |
| Component: | Build and Assembly | Assignee: | Roger Martínez <romartin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Svitak <jsvitak> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | etirelli, mbaluch, pzapataf |
| Target Milestone: | ER5 | ||
| Target Release: | 6.0.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-06 20:12:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Roger Martínez
2013-11-12 18:38:56 UTC
In addition, org.jbpm:jbpm-human-task-audit:jar should be included in jbpm core module too. Older commits: -------------- - https://github.com/droolsjbpm/kie-wb-distributions/commit/afc12fea7073ea892e7634708d132b5276ab37a1 - https://github.com/droolsjbpm/kie-wb-distributions/commit/b101940eb33abd3389d971733a076d40760a6e19 Commits from today: ------------------ - https://github.com/droolsjbpm/kie-wb-distributions/commit/3a9a43690a030ddeed53a5917afd0198167a070a - https://github.com/droolsjbpm/kie-wb-distributions/commit/8abfd8cc8eeb705e171e5fdf09828941305b01b2 The only pending point is "Remove org.jbpm:jbpmmigration:jar artifact for both bpms/brms". By removing it, some errors are displayed when trying to build&deploy a process: 20:58:25,173 WARN [org.drools.core.xml.ExtensibleXmlParser] (http-localhost/127.0.0.1:8080-1) (null: 2, 733): schema_reference.4: Failed to read schema document 'BPMN20.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 20:58:25,173 ERROR [org.drools.core.xml.ExtensibleXmlParser] (http-localhost/127.0.0.1:8080-1) (null: 2, 733): cvc-elt.1: Cannot find the declaration of element 'bpmn2efinitions'. 20:58:25,176 WARN [org.drools.core.xml.ExtensibleXmlParser] (http-localhost/127.0.0.1:8080-1) (null: 3, 63): schema_reference.4: Failed to read schema document 'BPMN20.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 20:58:25,177 WARN [org.drools.core.xml.ExtensibleXmlParser] (http-localhost/127.0.0.1:8080-1) (null: 4, 63): schema_reference.4: Failed to read schema document 'BPMN20.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 20:58:25,179 WARN [org.drools.core.xml.ExtensibleXmlParser] (http-localhost/127.0.0.1:8080-1) (null: 5, 66): schema_reference.4: Failed to read schema document 'BPMN20.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. It seems that some schema definition files are located in jbpmmigration and required by other core resources. I will try to move these to another jbpm core artifact and check if jbpmmigration can be removed from core module. The xsd definitions located in jbpmmigration artifact has been copied into jbpm-bpmn2 artifact, which is located in jbpm core module. So, the jbpm core module resource jbpmmigration has been removed. Commits master ============== https://github.com/droolsjbpm/jbpm/commit/325bd353072df00fb02a77c3157cb4bd73bb181c https://github.com/droolsjbpm/kie-wb-distributions/commit/7a93d9a22486a85caddea14569dad69371185858 Commits 6.0.x ============= https://github.com/droolsjbpm/jbpm/commit/c8b1e21cbd613e6b76eb418b587a0d5477b0bb33 https://github.com/droolsjbpm/kie-wb-distributions/commit/3b7be80cb54fb6e2ea9450975b204894fca0bf51 This issue describes rather internal organization of modules and their dependencies. This issue doesn't have a direct impact on customers. ER5 was already released with EAP 6.1.1 module support. Verified. |