Bug 1030286

Summary:	BPMN2 Modeler should not use 'jBPM5' in the name of a target runtime
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Jiri Svitak <jsvitak>
Component:	Eclipse Tooling	Assignee:	Robert (Bob) Brodt <bbrodt>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marek Baluch <mbaluch>
Severity:	low	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	kverlaen, mbaluch
Target Milestone:	ER5
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 20:10:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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'.