Bug 1033542 - knowledge-api is missing org.drools.time.SessionPseudoClock
Summary: knowledge-api is missing org.drools.time.SessionPseudoClock
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER6
: 6.0.0
Assignee: Mario Fusco
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 10:52 UTC by Marek Winkler
Modified: 2014-08-06 20:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:17:48 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marek Winkler 2013-11-22 10:52:23 UTC 
Description of problem:

The legacy Drools knowledge-api does not contain the interface org.drools.time.SessionPseudoClock. This breaks backward compatibility with BRMS 5, therefore I am setting severity to high.

Version-Release number of selected component (if applicable):

Drools 6.0.0-SNAPSHOT
BRMS 6.0.0 ER4
Comment 1 Mario Fusco 2013-11-25 15:45:43 UTC 
The SessionPseudoClock is present in a different package: org.drools.core.time in drools-core.

We did this renaming (together with many others) to make drools osgi compliant so I don't think I could duplicate the SessionPseudoClock interface in the old package without breaking this.
Comment 2 Edson Tirelli 2013-11-26 15:51:26 UTC 
Marek,

There are a few things like this one that we can't do for backward compatibility. At the same time, this is a simple fix (just an import change). 

I am moving this to MODIFIED. Please re-evaluate and return to us if it needs to be discussed further.
Comment 3 Marek Winkler 2014-01-10 09:24:55 UTC 
Ok, thanks for the explanation. Since it is clear now that we cannot achieve 100 % backward compatibility even with knowledge-api, I believe we can leave the API as is, provided these differences from 5.3.1 API are documented.
Note You need to log in before you can comment on or make changes to this bug.