Bug 1037572 - Incremental compilation fails with declared types
Summary: Incremental compilation fails with declared types
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: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 11:54 UTC by Mario Fusco
Modified: 2014-08-06 20:15 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:15:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker DROOLS-363 0 Major Resolved Incremental compilation fails with declared types 2018-05-17 09:17:34 UTC

Description Mario Fusco 2013-12-03 11:54:06 UTC 
Incremental compilation doesn't work if the newly added drl contains a declared type.
Comment 1 Mario Fusco 2013-12-03 11:55:17 UTC 
Fixed by https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/c3b5b46b1 and https://github.com/droolsjbpm/drools/commit/b88dab153
Comment 3 JBoss JIRA Server 2013-12-06 01:33:35 UTC 
Davide Sottara <dsotty> updated the status of jira DROOLS-363 to Reopened
Comment 4 JBoss JIRA Server 2013-12-06 01:33:35 UTC 
Davide Sottara <dsotty> made a comment on jira DROOLS-363

If the new DRL contains a REDECLARATION of a previously declared type X, and any other class Y is generated during its compilation process, a package-level rewire of X might "orphan" existing instances. Should they match any rule, a ClassCastException will be thrown.
Comment 5 JBoss JIRA Server 2013-12-09 11:58:19 UTC 
Mario Fusco <mario.fusco> updated the status of jira DROOLS-363 to Resolved
Comment 6 Tomas Schlosser 2014-01-07 10:36:43 UTC 
Both commits are in product repository. Since the incremental build is internal feature and test for this fix was provided in community, I mark this issue as verified.
Note You need to log in before you can comment on or make changes to this bug.