Bug 1328184 - It is not possible to install optaplanner-engine feature in OSGI environment
Summary: It is not possible to install optaplanner-engine feature in OSGI environment
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: OptaPlanner
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: CR1
: 6.3.0
Assignee: Geoffrey De Smet
QA Contact: Jiri Petrlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 15:41 UTC by Jiri Petrlik
Modified: 2020-03-27 19:11 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Jiri Petrlik 2016-04-18 15:41:56 UTC
Description of problem:

It is not possible to install optaplanner-engine feature in JBoss Fuse 6.2.1. This bug is caused by following commits for BZ#1321790:
https://github.com/droolsjbpm/droolsjbpm-integration/pull/406
https://github.com/droolsjbpm/droolsjbpm-integration/pull/407

The problem is that "optaplanner-persistence-common" and "optaplanner-persistence-xstream" bundles have the same Bundle-SymbolicName - "org.optaplanner.persistence.xstream". See "pom.xml" files for these modules. It is necessary to change "optaplanner-persistence-common" bundle symbolic name.

Version-Release number of selected component (if applicable):
BxMS 6.3.0.ER3

How reproducible:


Steps to Reproduce:
1. Install optaplanner-engine feature in Jboss Fuse 6.2.1.

Actual results:
optaplanner-persistence-xstream bundle is not installed

Expected results:
optaplanner-persistence-xstream bundle should be installed


Additional info:

Comment 2 Geoffrey De Smet 2016-04-19 13:54:52 UTC
It's a stupid copy-paste error by yours truly in optaplanner-persistence-common's pom.xml. To bad that none of the unit tests detect it (I ran all tests both in optaplanner and in drools-osgi.)

Fixed on master
  http://github.com/droolsjbpm/optaplanner/commit/2d6d6a406
Fixed on 6.4.x
  http://github.com/droolsjbpm/optaplanner/commit/908afbf06

Comment 3 Jiri Petrlik 2016-04-28 10:02:04 UTC
The problem with wrong bundle symbolic name of bundle "optaplanner-persistence-common" was fixed in BxMS 6.3.0.CR1. Now, it is possible to successfully install "optaplanner-engine" feature.


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