Hi I&#39;m currently working on an implementation of a new type of problem type namely Warnings, to solve the following JIRA&#39;s: <div><span class="Apple-style-span" style="color: rgb(102, 102, 102); font-family: helvetica, arial, freesans, clean, sans-serif; font-size: 13px; line-height: 18px; background-color: rgb(255, 255, 255); ">JBRULES-3124, JBRULES-3063, JBRULES-2730</span></div>
<div><span class="Apple-style-span" style="color: rgb(102, 102, 102); font-family: helvetica, arial, freesans, clean, sans-serif; font-size: 13px; line-height: 18px; background-color: rgb(255, 255, 255); "><br></span></div>
<div><span class="Apple-style-span" style="color: rgb(102, 102, 102); font-family: helvetica, arial, freesans, clean, sans-serif; font-size: 13px; line-height: 18px; background-color: rgb(255, 255, 255); ">One of the JIRA&#39;s deal with the detection of duplicate rules and another with detection of duplicate functions.</span></div>
<div>The question I have is in regards to this is, the current implementation allows for rules and functions to be overridden by functions and rules defined in different .drl files.</div><div>In order to not break backwards compatibility and allow people to continue with this behavior we could just create a warning for these types of issues which is reported through a new getProblems(ProblemType... problemTypes) to get the problem types you are interested in, we will leave the legacy method getErrors() for backward compatibility. Another approach or complementary approach is to for certain types of these Warnings configure the compiler to be more or less strict, which in turn would switch the Type of these issues from Warning to Error. Is this something that&#39;s desirable or would it be sufficient to just report these issues as warnings and leave the responsibility to the user to halt execution if certain Warnings exists?</div>
<div><br></div><div>Kind Regards</div><div><br></div><div>Mikael (gwendo)</div>