[
http://jira.jboss.com/jira/browse/JBPM-1041?page=comments#action_12372717 ]
Ronald van Kuijk commented on JBPM-1041:
----------------------------------------
hmmm I was sure I also added a comment... here we go
- old version of GPD, very old version
- GPD has it's own project in jira, called GPD:
http://jira.jboss.com/jira/browse/GPD
- very little info
- different requests in one issue
Now more constructive answers
1: totally up to you. use the console, create/use ant tasks, create you own app... pick
one...if you want different deployment methods between test and production, then do so..
if not, keep them the same.
2: Runtime at the 'process' level? e.g. when a certain task is encountered? then
file a jira issue for the GPD. This is *not* just a documentation issue but a very
complex thing to build. You can do this in unit tests very easily btw...
jBPM documentation changes to include Deployment and Debug steps.
-----------------------------------------------------------------
Key: JBPM-1041
URL:
http://jira.jboss.com/jira/browse/JBPM-1041
Project: JBoss jBPM
Issue Type: Feature Request
Components: Documentation
Affects Versions: jBPM GPD 3.0.7
Environment: All
Reporter: Satya Satyamoorthy
Assigned To: Tom Baeyens
Fix For: jBPM GPD 3.0.7
Please add adequate documentation listing the steps to
1. Deploy the processes to different environments - such as test, user acceptance,
production etc. from the RHDS.
2. Set breakpoints and Trace and Debug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira