Bug 1030286 - BPMN2 Modeler should not use 'jBPM5' in the name of a target runtime
Summary: BPMN2 Modeler should not use 'jBPM5' in the name of a target runtime
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ER5
: 6.0.0
Assignee: Robert (Bob) Brodt
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-14 09:53 UTC by Jiri Svitak
Modified: 2015-06-02 01:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:10:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jiri Svitak 2013-11-14 09:53:55 UTC 
This issue is not a serious one, but rather cosmetical. BPMN2 Modeler should not use 'jBPM5' in the name of the target runtime. I think that this might confuse our customers. It should be renamed to 'jBPM6' or just 'jBPM'. What do you think?

My env:
BPMN2 Editor 1.0.0.201311042148, JBDS 7.0.1.GA (Build id: GA-v20130930-2238-B7).
Comment 1 Kris Verlaenen 2013-11-26 14:12:12 UTC 
I would recommend simply using jBPM (as we'll reach jBPM7 before we know it ;)).  It's not applicable for jBPM4 or lower, but I guess that is what most users would expect anyway.
Comment 2 Kris Verlaenen 2013-11-26 21:15:25 UTC 
Should be fixed according to Bob in v1.0.1
Comment 3 Marek Baluch 2013-12-03 20:53:08 UTC 
Verified on JBTIS 4.1.3.Beta5. (BPMN2 Editor v 1.0.0)

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