[Mono-bugs] [Bug 666567] New: gd2i tool doesn't produce ignore entries for ALL of the defects
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Mon Jan 24 07:38:18 EST 2011
https://bugzilla.novell.com/show_bug.cgi?id=666567
https://bugzilla.novell.com/show_bug.cgi?id=666567#c0
Summary: gd2i tool doesn't produce ignore entries for ALL of
the defects
Classification: Mono
Product: Mono: Tools
Version: 2.10.x
Platform: PC
OS/Version: Windows Server 2003
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Gendarme
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: knocte at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US)
AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
If I run the gendarme 2.10 preview against my DLL (no options when called), it
reports 77 defects.
Now, if I make it generate an XML file of the defects, and use it as input for
gd2i, then later use gendarme.exe with the --ignore option targeting the
baseline I created, I still get 12 defects.
Examples of the defects still found:
------------------------------------------------------------
1. MarkAssemblyWithCLSCompliantRule
Problem: This assembly is not decorated with the [CLSCompliant] attribute.
* Severity: High, Confidence: Total
* Target: SevenDigital.Api.Payments.Web, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null
Solution: Add this attribute to ease the use (or non-use) of your assembly by
CLS consumers.
More info available at:
http://www.mono-project.com/Gendarme.Rules.Design#MarkAssemblyWithCLSCompliantRule
------------------------------------------------------------
2. AvoidDeepNamespaceHierarchyRule
Problem: The depth of the namespace hierarchy is getting out of control.
* Severity: Medium, Confidence: High
* Target: SevenDigital.Api.Payments.Web, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null
* Location: SevenDigital.Api.Payments.Web.Resources
Solution: Try to keep the depth below 4, with an additional one for
specialization (e.g. Design, Interop, Permissions).
More info available at:
http://www.mono-project.com/Gendarme.Rules.Naming#AvoidDeepNamespaceHierarchyRule
Actually, just checked, and these defect types are the only ones that are
reported in this last step.
Reproducible: Always
--
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