Bug 1295518 - 4 or more shadow variables might trigger cyclic source dependencies exception when that's not the case
Summary: 4 or more shadow variables might trigger cyclic source dependencies exception...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: OptaPlanner
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR1
: 6.3.0
Assignee: Geoffrey De Smet
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On: 1295363
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 18:20 UTC by Alessandro Lazarotti
Modified: 2020-03-27 19:04 UTC (History)
3 users (show)

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

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

Description Alessandro Lazarotti 2016-01-04 18:20:19 UTC 
+++ This bug was initially created as a clone of Bug #1295363 +++

Description of problem:
see JIRA: https://issues.jboss.org/browse/PLANNER-490

as Geoffrey proposed, I would like to see this backported in 6.3x

--- Additional comment from JBoss Product and Program Management on 2016-01-04 04:20:19 EST ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Geoffrey De Smet on 2016-01-04 05:37:43 EST ---

Fixed with this commit on 6.3.x
  https://github.com/droolsjbpm/optaplanner/commit/f1db72e5c
It was already fixed on master.
Comment 1 Geoffrey De Smet 2016-01-05 12:26:40 UTC 
Already backported to 6.3.x because the original BZ 1295363 was about backporting it (the JIRA PLANNER-490 was about fixing it on master).

But it's better to create a JIRA/BZ too many than too little ;) Keep them coming!

*** This bug has been marked as a duplicate of bug 1295363 ***
Comment 3 Alessandro Lazarotti 2016-01-05 12:54:27 UTC 
Setting as MODIFIED, given that this BZ targets product 6.3, not the patch update 6.2.1.
Jira issue tracker is not for product yet and it is not verified by QA.
Comment 4 jvahala 2016-02-10 12:05:21 UTC 
Tests are ok, verified
Note You need to log in before you can comment on or make changes to this bug.