[jboss-jira] [JBoss JIRA] Assigned: (JBRULES-804) Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project)

Wed Apr 18 20:09:33 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBRULES-804?page=all ]

Michael Neale reassigned JBRULES-804:
-------------------------------------

    Assignee: Kris Verlaenen  (was: Mark Proctor)

Might be worth thinking about.

If you think its not needed, we could provide documentation on how to set exclusion rules for the builder.

> Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project)
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-804
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-804
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 3.1-m1
>         Environment: WinXP, Sun JRE 1.4.2_12
>            Reporter: Bree VanOss
>         Assigned To: Kris Verlaenen
>            Priority: Minor
>
> The Eclipse "Drools Builder" is validating every Excel (.xls) in my rules project. 
> Apparently this feature was added to 3.1-M1 by Kris. I really like the idea of validating decision tables in Eclipse, my issue is that we have FIT tests (in Excel) in a separate source folder in our "rules project". These .xls files are falsely being identified as decision tables with a ton of problems. Validation also seems to take much longer than it does with the 3.0.x branch (like from 30 seconds in 3.0 to to 5 minutes in 3.1 !?!?). Though the two issues may be related.
> A common way of dealing with this problem in Eclipse is to allow for ant-like "source path include/exclude" patterns.
> i.e. exclude test/**/*.xls
> For that matter it would be nice to have the same thing for standard DRL files. The validation of a large rule base can take some time and randomly results in exceptions much of the time. Once I've tested and verified a set of rules I could (optionally) exclude them from validation. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira