Hi Peter, It sounds like one of the difficulties is in "seeing" what is taking up space, and what kinds of things a person might want to consider to do refactoring.
One idea to think about: could there be some new kind of tracing or reporting that could be added (conditionally, as it might take space and/or slow things down) that a user having these kinds of problems could run with to get a useful report on where to look? Also, I'm wondering if there are any "findbugs" kinds of tooling (or compilation mode) (that could be reasonably developed) that users could run against their rules, to guide them toward suspicious constructs, etc. Just random thoughts... -Marshall On 4/30/2017 7:01 AM, Peter Klügl (JIRA) wrote: > Peter Klügl created UIMA-5414: > --------------------------------- > > Summary: Ruta: config param for max amount of rule and rule > element matches > Key: UIMA-5414 > URL: https://issues.apache.org/jira/browse/UIMA-5414 > Project: UIMA > Issue Type: New Feature > Components: Ruta > Affects Versions: 2.6.0ruta > Reporter: Peter Klügl > > > Ruta: config param for max amount of rule and rule element matches. If > exceeded, an runtime exception is throw with the name of the script and the > verbalization of the rule/rule element. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.15#6346) >
