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

Bug 881044

Summary: Drools project debugging does not stop at breakpoint with BRMS 5.3.1.ER4
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: jgargula
Component: Tooling (JBDS)Assignee: John Graham <jgraham>
Status: CLOSED DUPLICATE QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.1CC: brms-jira, lpetrovi, mvecera, tkobayas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-03 07:12:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jgargula 2012-11-28 13:47:28 UTC 
Description of problem:
Debugging of Drools project doesn't stop at breakpoints and runs without stopping to the end.


Version-Release number of selected component (if applicable):
- JBoss Developer Studio Drools plugin:
  - JBoss Drools Core    5.3.4.201210090942
  - JBoss Drools Guvnor  5.3.4.201210090942
  - JBoss Drools Task    5.3.4.201210090942

- BRMS runtime         5.3.1.BRMS-ER4

- JBDS 5.0.0.Final


How reproducible:
Follow next steps

Steps to Reproduce:
1. create new Drools runtime and set it as default
2. create new Drools Project with default Drools runtime and add all sample codes
3. open src/main/rules/Sample.drl and add breakpoint to 9th line
4. right click on src/main/java/DroolsTest.java and execute Debug as Drools application

  
Actual results:
- application is running to the end without stopping at breakpoint


Expected results:
- execution should stop at the breakpoint


Additional info:
- debugging is working properly with BRMS runtime 5.3.1.ER3
Comment 2 Toshiya Kobayashi 2013-04-03 07:12:33 UTC 

*** This bug has been marked as a duplicate of bug 947741 ***