I'd like to have the following features, but wanted to get everyone's feedback. 1) The ability to read in effort from the XML files. User Story: User runs Windup report and doesn't agree with the effort estimate. They would like to change the effort for a Java rule and rerun Windup, but aren't technical enough to recompile Windup. Proposed Solution: Having a utility that we could use to easily look up a property from the Windup XML configuration would be a great solution for this. That way, it makes it easy for people to modify the effort. 2) The ability to override and disable rules from the XML. User Story: A Java rule is not providing anticipated output and needs to be excluded from the report. Proposed Solution: Have a simple registry of disabled rules in the XML, where the qualified Java class is provided that needs to be disabled / skipped.

Brad Davis Senior Manager, Red Hat Consulting Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com _______________________________________________ windup-dev mailing list windup-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev

Sure; makes sense to me. I figured you would just comment out XML rules but there isn't a way to do that with Java rules. Rule name is fine though. Sent from my iPhone > On Sep 2, 2015, at 2:01 PM, Jess Sightler <jsightle(a)redhat.com&gt; wrote: > > > >> On 08/04/2015 10:41 AM, Brad Davis wrote: >> I'd like to have the following features, but wanted to get everyone's feedback. >> >> 1) The ability to read in effort from the XML files. >> >> User Story: User runs Windup report and doesn't agree with the effort estimate. They would like to change the effort for a Java rule and rerun Windup, but aren't technical enough to recompile Windup. >> Proposed Solution: Having a utility that we could use to easily look up a property from the Windup XML configuration would be a great solution for this. That way, it makes it easy for people to modify the effort. >> >> >> 2) The ability to override and disable rules from the XML. >> >> User Story: A Java rule is not providing anticipated output and needs to be excluded from the report. >> Proposed Solution: Have a simple registry of disabled rules in the XML, where the qualified Java class is provided that needs to be disabled / skipped. > > I think this is a good idea, although I think that we should base it on > the Rule Provider ID (or optionally rule id) rather than on the class name. > > > >> >> >> Brad Davis >> Senior Manager, Red Hat Consulting >> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com >> >> >> _______________________________________________ >> windup-dev mailing list >> windup-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/windup-dev > > _______________________________________________ > windup-dev mailing list > windup-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/windup-dev _______________________________________________ windup-dev mailing list windup-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev