[
https://issues.jboss.org/browse/JBIDE-8946?page=com.atlassian.jira.plugin...
]
Martin Malina commented on JBIDE-8946:
--------------------------------------
OK, it makes sense as you say it. The problem that I still see is that users could get
confused - there is a Remove button, but it is shaded out... Ideally, there could be some
explanation of the behavior ("A jBPM runtime cannot be removed if it is the only one
existing"), but I don't know where we would put it.
But at least I think we could document this, WDYT?
I checked
http://docs.jboss.org/tools/3.2.0.GA/en/jboss_jbpm_ref_guide/html_single/... and I
think that this information would fit nicely in the chapter "2.1. JBoss jBPM Runtime
Installation" somewhere around this article:
{quote}
Select Window → Preferences → JBoss jBPM → Runtime Locations. Here you can add, edit and
remove JBoss jBPM installation locations. Click the Add button. In the subsequent dialog
box enter a name for a newly added jBPM runtime and point to the correct location of this
package on your file system. Click the OK button twice to save the changes.
{quote}
Unable to remove jBPM runtime
-----------------------------
Key: JBIDE-8946
URL:
https://issues.jboss.org/browse/JBIDE-8946
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtimes
Affects Versions: 3.2.1.M1
Environment: Mac OS X 10.6 Snow Leopard
jbdevstudio-product-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar
Reporter: Martin Malina
Assignee: Koen Aers
Fix For: 3.3.0.M2, 3.2.x
Attachments: screenshot-1.jpg
When you add SOA-P 5.1, it will add a jBPM runtime among other things. It's not
possible to remove this runtime. All other runtimes, including Seam and Drools, can be
removed without a problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira