Bug 1293904

Summary: [DOC] Maven documentation is not enough to start a project
Product: [Retired] JBoss BPMS Platform 6 Reporter: Alessandro Lazarotti <alazarot>
Component: DocumentationAssignee: Dawn Eisner <deisner>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: brms-docs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:47:37 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 Alessandro Lazarotti 2015-12-23 13:11:15 UTC 
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BRMS/6.2/html/Installation_Guide/Dependency_Management.html

Section Number and Name: 
6.5. DEPENDENCY MANAGEMENT

Describe the issue: 
Dev users do not have any information about which dependencies should be add to pom.xml to star a project with BRMS or BPM Suite.

Such set of dependencies can vary depending of customer project but we should offer some small sets that customer can use, including the versions used with the product in the 6.2.0 version.

Suggestions for improvement: 

Such pom.xml descriptions must contain references for projects that user needs to use at least:
- BPMN2 Processes with Human Tasks
- Plain rules
- Rules with Decision Tables.
- tests / examples (jbpm-example artifact  )

See that other information must be provided, as example the version of BOMs and  dependencies, explaining that such versions can be changed in future patch releases.