[JBoss JIRA] (JBRULES-3289) PackageBuilder.getErrors().toString() should use a clearer layout (indentation and empty lines)
5:51 a.m.
PackageBuilder.getErrors().toString() should use a clearer layout (indentation and empty
lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta1
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:51 a.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-3289:
--------------------------------------
Description:
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
was:
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta1
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:15 a.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-3289:
--------------------------------------
Fix Version/s: 5.4.0.Beta2
(was: 5.4.0.Beta1)
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta2
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 a.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-3289:
--------------------------------------
Fix Version/s: 5.4.0.Beta3
(was: 5.4.0.Beta2)
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta3
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 a.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-3289:
----------------------------------
Fix Version/s: 5.4.0.Final
(was: 5.4.0.CR1)
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.4.0.Final
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:01 a.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-3289:
----------------------------------
Fix Version/s: 5.5.0.Beta1
(was: 5.4.0.Final)
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.5.0.Beta1
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Michael Anstis updated JBRULES-3289:
------------------------------------
Fix Version/s: 5.5.0.CR1
(was: 5.5.0.Beta1)
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 5.5.0.CR1
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 p.m.
[
https://issues.jboss.org/browse/JBRULES-3289?page=com.atlassian.jira.plug...
]
Michael Anstis updated JBRULES-3289:
------------------------------------
Fix Version/s: 6.0.0.Beta1
(was: 5.5.0.CR1)
PackageBuilder.getErrors().toString() should use a clearer layout
(indentation and empty lines)
-----------------------------------------------------------------------------------------------
Key: JBRULES-3289
URL: https://issues.jboss.org/browse/JBRULES-3289
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Fix For: 6.0.0.Beta1
It's hard to read the compilation errors in drools (and parsing them in my head).
The main problem is parsing the points where the next compile error begins.
By adding some indentation and removing some confusing empty lines this can be made a lot
clearer.
BEFORE:
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
// 2 extra empty lines
{code}
AFTER (with indentation):
{code}// Start
Unable to resolve ObjectType 'NotExistingClass' : [Rule
name='serviceLocationSpread']
Unable to Analyse Expression location == $location:
[Error: unable to resolve method using strict-mode:
org.drools.planner.examples.machinereassignment.domain.MrProcessAssignment.$location()]
[Near : {... location == $location ....}]
^
[Line: 112, Column: 68] : [Rule name='serviceLocationSpread']
Rule Compilation error : [Rule name='serviceLocationSpread']
org/drools/planner/examples/machinereassignment/solver/Rule_serviceLocationSpread_503372c0945a4f2287a530f4ff3aee40.java
(9:2095) : $location cannot be resolved
{code}
Just compare those two. The second one is easier to read diagonally and understand
what's going wrong.
It might be even better if the "Rule Compliation error" part comes first
(following the context-first guideline):
So instead of:
{code}
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error A
Rule Compilation error A details
Error B1
Error B1 details
Error B2
Error B2 details
Rule Compilation error B
Rule Compilation error B details
{code}
We get:
{code}
Rule Compilation error A
Rule Compilation error A details
Error A1
Error A1 details
Error A2
Error A2 details
Rule Compilation error B
Rule Compilation error B details
Error B1
Error B1 details
Error B2
Error B2 details
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4448
days inactive
4794
days old
7 comments
5 participants
participants (5)
-
Geoffrey De Smet (Created) (JIRA) -
Geoffrey De Smet (JIRA)
-
Geoffrey De Smet (Updated) (JIRA)
-
Michael Anstis (JIRA)
-
Toni Rikkola (JIRA)