[Mono-bugs] [Bug 671178] New: Be able to configure the "SuccessLowerLimit" configuration for AvoidLackOfCohesionOfMethodsRule Rule

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Feb 11 01:36:24 EST 2011



           Summary: Be able to configure the "SuccessLowerLimit"
                    configuration for AvoidLackOfCohesionOfMethodsRule
    Classification: Mono
           Product: Mono: Tools
           Version: 2.10.x
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Gendarme
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: mathias.kluba at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US)
AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.84 Safari/534.13


Gendarme is a wonderful tool and I use it a lot.
I'm using it with Sonar .Net plugin
This one is using the gendarme.exe command line, with a XML ruleset as

I wish to be able to configure the property "SuccessLowerLimit" to set my limit
for AvoidLackOfCohesionOfMethodsRule violations.

The property is a Double (I can see it in Reflector) and the default value is
When I try to edit the value in the ruleset XML to be "0.4" for example, it
doesn't work, because gendarme.exe is checking the XML with its XSD which
doesn't allow non Interger values for rules parameters.

Is it possible to edit the XSD to remove this restriction?
Where am I suppose to submit bugs for Gendarme?


Reproducible: Always

Steps to Reproduce:
1. Write a custom ruleset xml
2. Add a rule with a parameter of type "Double" and change the value du be
3. Run gendarme.exe with the ruleset as parameter
Actual Results:  
Crash: the XML can't be validated by XSD

Expected Results:  
Use the double value for the gendarme rule

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list