Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 758996

Summary:	JBDS installs wrong Drools runtime
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Lukáš Petrovický <lpetrovi>
Component:	Tooling (JBDS)	Assignee:	Kris Verlaenen <kverlaen>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Vecera <mvecera>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA	CC:	ldimaggi, rzhang
Target Milestone:	---
Target Release:	BRMS 5.3.0.GA
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:14:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukáš Petrovický 2011-12-01 07:47:24 UTC

When you open JBDS and ask it to create new Drools runtime, you get a
dialog that gives you two options:

- Either you use your own runtime, perhaps one you've received from Red
Hat in a BRMS package.
- Or you have JBDS generate the runtime for you.

There is nothing to talk about in the first case - that's what I've
always done when I wanted to work with JBDS. The problem lies in the
second case - because when you select it, you get a runtime based on
the project binaries, not the product binaries.

Also, this runtime is Drools 5.2, not Drools 5.3. Not that it matters, because it most probably won't be compatible with BRMS 5.3 anyway.

Comment 2 lcarlon 2012-05-03 03:35:37 UTC

JBDS tends to work with the projects by default.

The Getting Started documentation for BRMS instructs users to install the runtime from the BRMS packages they have downloaded. I'm not sure what else we could do about option number 2.

Thanks
Lee

Comment 3 Kris Verlaenen 2012-05-09 15:29:14 UTC

The first case is definitely recommended, and afaik the documented strategy.

For option 2, the Drools & jBPM Eclipse plugin that accompanies BRMS 5.3 is built from the same branches as the product, and thus contains the same jars as BRMS 5.3.  So creating a runtime from the tooling should create a runtime compatible with BRMS 5.3 (not identical as it only contains a much smaller subset of all the jars).

I'm adding the need_info flag on this, to request additional feedback whether anything actually should be changed, and if so what.

Comment 4 Lukáš Petrovický 2012-05-25 11:55:32 UTC

This issue is/will be resolved when we get the Drools JBDS plugins built directly by productization. Nothing we can do until then.

Comment 5 Ryan Zhang 2012-06-13 09:32:42 UTC

This issue's fixes  have been picked by ER9. Please verify them on ER9.

Comment 6 Ryan Zhang 2012-06-14 02:14:30 UTC

Sorry, this is tools bug and it will only be availabe in SOA tools plugins.
Revert the target milestone field.

Comment 7 Len DiMaggio 2012-06-15 12:59:10 UTC

Link to: JBDS-1898

Comment 11 Red Hat Bugzilla 2025-02-10 03:14:28 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.