]
edurand commented on JBRULES-1339:
----------------------------------
Same problem with Eclipse on Windows : you have to use a variable to stop on a
breakpoint.
Debugging: Breakpoints are only considered for code with variables
------------------------------------------------------------------
Key: JBRULES-1339
URL:
http://jira.jboss.com/jira/browse/JBRULES-1339
Project: JBoss Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Eclipse IDE
Affects Versions: 4.0.3
Environment: Linux (Kubunut 7.10), Current Eclipse 3.2.x, Drools 4.0.3
Reporter: Michael Zimmermann
In my installation breakpoints in drl files are only recognized
if there is any variable involved. Here is a small example
1) Works ok, while debugging the application stops at the breakpoint in
System.out.println()
rule "TestRule"
when
eval (1==1)
then
int i = 1;
System.out.println("Breakpoint ok" +i);
end
2) The breakpoint in System.out.println() is ignored. The rule fires
nevertheless....
rule "TestRule"
when
eval (1==1)
then
int i = 1;
System.out.println("Breakpoint ignored");
end
Tested via the Debug > As > Drools
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: