Return-Path: 
 <dev-return-102925-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
X-Original-To: apmail-cocoon-dev-archive@www.apache.org
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B6C0B7BB0
	for <apmail-cocoon-dev-archive@www.apache.org>;
 Fri,  5 Aug 2011 09:26:34 +0000 (UTC)
Received: (qmail 92682 invoked by uid 500); 5 Aug 2011 09:26:34 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 92327 invoked by uid 500); 5 Aug 2011 09:26:20 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 92318 invoked by uid 99); 5 Aug 2011 09:26:16 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2011 09:26:16 +0000
X-ASF-Spam-Status: No, hits=-5.0 required=5.0
	tests=RCVD_IN_DNSWL_HI,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [153.46.252.105] (HELO mail1.telekurs.com) (153.46.252.105)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2011 09:26:10 +0000
Received: from svzpexcasht11.base.dom (Not Verified[10.23.199.36]) by
 mail1.telekurs.com (using TLS: SSLv23)
	id <B4e3bb71c0000>; Fri, 05 Aug 2011 11:25:48 +0200
Received: from LPZHWMEXE11.base.dom
 ([fe80:0000:0000:0000:7957:035c:66.63.43.233]) by svzpexcasht11.base.dom
 ([10.23.199.36]) with mapi; Fri, 5 Aug 2011 11:25:48 +0200
From: "Nathaniel, Alfred" <Alfred.Nathaniel@six-group.com>
To: "'dev@cocoon.apache.org'" <dev@cocoon.apache.org>
Date: Fri, 5 Aug 2011 11:25:47 +0200
Subject: RE: Filtering out (some) Sonar violations
Thread-Topic: Filtering out (some) Sonar violations
Thread-Index: AcxTPAvjmY9MGnT6QDSXk2cNGlbKowAEXJaQ
Message-ID: <A98F6459E618D84E8D2D430C4F26D9B60ACB40523C@LPZHWMEXE11.base.dom>
References: <4E3B92A4.5000909@apache.org>
In-Reply-To: <4E3B92A4.5000909@apache.org>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-CH
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Francesco,

I am a big fan of Findbugs and persueing a zero-warnings policy.
In other projects we use a Findbugs exclude filter file to
disable warnings and document the deliberation for doing so.

Sonar should foresee to pull such an exclude filter from the
project's code base.

NB we also exclude XFB_XML_FACTORY_BYPASS with reason
"axis.client.Stub requires specific axis.message.SOAPHeaderElement".

Cheers, Alfred.

-----Original Message-----
From: Francesco Chicchiricc=F2 [mailto:ilgrosso@apache.org]=20
Sent: Freitag, 5. August 2011 08:50
To: dev@cocoon.apache.org
Subject: Filtering out (some) Sonar violations

...

My proposal would be to open a issue to INFRA in order to ask for=20
disabling these two rules: do you see any problem, with this?

For my personal experience about Findbugs, PMD and Checkstyle, it is=20
rather impossible to satisfy all the rules (thus bringing the number of=20
violations to zero); however, I personally think that reducing the huge=20
amount that we have at the moment would dramatically improve Cocoon 3's=20
source code quality.

...

The content of this e-mail is intended only for the confidential use of t=
he person addressed.=20
If you are not the intended recipient, please notify the sender and delet=
e this e-mail immediately.
Thank you.