Bug 781178 (SOA-3681)

Summary: Restore jbpm-jpdl/deploy directory in SOA build
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Martin Weiler <mweiler>
Component: Build Process, JBPM - standaloneAssignee: Julian Coleman <jcoleman>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP05CC: jcoleman, mputz, mweiler
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3681
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 781179 (view as bug list) Environment:
Last Closed: Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Weiler 2012-01-03 13:36:35 UTC 
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008T5UU
project_key: SOA

In previous SOA-P versions, the $SOA_HOME/jbpm-jpdl/deploy directory contained artifacts that were useful for customers who want to deploy jBPM standalone, outside of the SOA platform. Due to a change in the build process, this directory is either empty (SOA-P 4.3 CP05), or contains the jsf-console.war only (SOA-P 5.2.0).

As some of the components that had been included in the deploy directory are not contained at some other place either (such as jbpm-enterprise.jar), the purpose of this task is to get the build modified again so that either the old format is restored, or the missing artifacts are included elsewhere.
Comment 2 Julian Coleman 2012-01-11 12:39:19 UTC 
Resolved with revision 10662 of:

  pom.xml
  src/main/assembly/soa.zip.xml
  src/main/resources/jbpm/autosetup.xml

Commit message:

  SOA-3681
  Update jBPM to 3.2.11.SP3 and restore jbpm-enterprise.jar and jbpm-service.sar
  to standalone jBPM (jpbm-jpdl directory).