Bug 1309947 - JBDS Business Process and Rules Development Extension Ships Wrong Features
Summary: JBDS Business Process and Rules Development Extension Ships Wrong Features
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 04:15 UTC by Justin Holmes
Modified: 2023-09-14 03:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:39:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Justin Holmes 2016-02-19 04:15:52 UTC
Description of problem:
After discussing with Bob Brodt, the JBDS installation process pulls in the "Bpmn2 Model Editor" and the "BPMN2 Process Editor" which have been removed from the community installation, but not product. This creates a very confusing experience for end users, because many editors are exposed for one asset.

Version-Release number of selected component (if applicable):
JBDS 8.1 - Plugin version 1.1.4.final
JBDS 9.0 - Plugin version 1.2.1.Final


How reproducible:
100%

Steps to Reproduce:
1. Install Business Process and Rule Development extension to JBDS
2. New->jbpm process
3. Right click created bpmn2 file -> Open With...

Actual results:
Menu has 3 "Bpmn2" options: 
"Bpmn2 Diagram Editor"
"Bpmn2 Model Editor"
"BPMN2 Process Editor"

Expected results:
Only "Bpmn2 Diagram Editor" should be present


Additional info:

Comment 2 Jozef Marko 2016-02-22 07:49:00 UTC
Still reproducible on:
jbds-9.1.0.Beta2_jbdsis-9.0.0.Beta1, BPMN2 Modeler - 1.2.3.CR2-v20160209-2002

Comment 3 Jozef Marko 2016-04-07 10:44:30 UTC
Hello Bob. Is this issue valid or is there need for 3 different editors?

Comment 4 Red Hat Bugzilla 2023-09-14 03:18:10 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.