[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8228) Default jBPM Server Deployer set to gpd-deployer/upload
[
https://issues.jboss.org/browse/JBIDE-8228?page=com.atlassian.jira.plugin...
]
Koen Aers resolved JBIDE-8228.
------------------------------
Resolution: Rejected
After talking to Max it seems better not to address this issue. The situation as it is now
reflects the project/product split. Maybe it would be good if the jBPM project would use
the same url as defined in the SOA-P product, but that would have to be changed in the
runtime project first.
Default jBPM Server Deployer set to gpd-deployer/upload
-------------------------------------------------------
Key: JBIDE-8228
URL: https://issues.jboss.org/browse/JBIDE-8228
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jbpm
Affects Versions: 3.2.0.CR1
Environment: JBT 3.2.CR1, Linux 64
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.2.0.CR2 (tentative), 3.2.1
Currently default server deployer (jBPM Process -> Deployment Page -> Server
Deployer) is set to /jbpm-console/upload. For recent JBoss runtimes (SOA-P specifically)
default jBPM deployer is "gpd-deployer/upload". If there are no other reasons
for keeping the old value, I suggest to change it to "gpd-deployer/upload".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira