[prev in list] [next in list] [prev in thread] [next in thread]
List: sonar-user
Subject: Re: [sonar-user] sonar.jacoco.excludes logic?
From: Scott Wolk <swolk () netbase ! com>
Date: 2012-02-28 17:27:04
Message-ID: CB724E27.2E8C9%swolk () netbase ! com
[Download RAW message or body]
Thanks Freddy! Logged an improvement as http://jira.codehaus.org/browse/SON=
AR-3295
Scott
From: Freddy Mallet <freddy.mallet@gmail.com<mailto:freddy.mallet@gmail.com=
>>
Reply-To: "user@sonar.codehaus.org<mailto:user@sonar.codehaus.org>" <user@s=
onar.codehaus.org<mailto:user@sonar.codehaus.org>>
Date: Tue, 28 Feb 2012 05:22:57 -0600
To: "user@sonar.codehaus.org<mailto:user@sonar.codehaus.org>" <user@sonar.c=
odehaus.org<mailto:user@sonar.codehaus.org>>
Subject: Re: [sonar-user] sonar.jacoco.excludes logic?
Hi Scott,
Feel free to create a JIRA ticket in order to ask for changing this behavio=
r. You're not the first one to complain about this.
Thanks
Freddy
-----
twitter.com/FreddyMallet<https://twitter.com/FreddyMallet>
Sonar for Continuous Inspection
On Tue, Feb 28, 2012 at 1:07 AM, Scott Wolk <swolk@netbase.com<mailto:swolk=
@netbase.com>> wrote:
Hi there, we want to switch from clover code coverage to jacoco. There is a=
couple of projects that exclude classes from code coverage, but we still r=
un rules on them for violations. I tried using sonar.jacoco.excludes but in=
stead of excluding that code for coverage, it just assigns 0% to them so th=
at it lowers the coverage numbers for their components. I can't understand =
the logic of this. Shouldn't it exclude those classes from instrumentation =
AND the coverage report like clover and cobertura excludes? It would be gre=
at to change this behavior instead of waiting for SONAR-766 to be addressed=
.
Thanks,
Scott
[Attachment #3 (text/html)]
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; \
font-family: Calibri, sans-serif; "><div><div><div>Thanks Freddy! Logged an \
improvement as <a \
href="http://jira.codehaus.org/browse/SONAR-3295">http://jira.codehaus.org/browse/SONAR-3295</a></div></div></div><div><br></div><div>Scott</div><div><br></div><span \
id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; \
text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; \
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt \
solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span \
style="font-weight:bold">From: </span> Freddy Mallet <<a \
href="mailto:freddy.mallet@gmail.com">freddy.mallet@gmail.com</a>><br><span \
style="font-weight:bold">Reply-To: </span> "<a \
href="mailto:user@sonar.codehaus.org">user@sonar.codehaus.org</a>" <<a \
href="mailto:user@sonar.codehaus.org">user@sonar.codehaus.org</a>><br><span \
style="font-weight:bold">Date: </span> Tue, 28 Feb 2012 05:22:57 -0600<br><span \
style="font-weight:bold">To: </span> "<a \
href="mailto:user@sonar.codehaus.org">user@sonar.codehaus.org</a>" <<a \
href="mailto:user@sonar.codehaus.org">user@sonar.codehaus.org</a>><br><span \
style="font-weight:bold">Subject: </span> Re: [sonar-user] sonar.jacoco.excludes \
logic?<br></div><div><br></div>Hi Scott, <div><br></div><div>Feel free to create \
a JIRA ticket in order to ask for changing this behavior. You're not the first one to \
complain about this.</div><div><br></div><div>Thanks</div><div>Freddy</div><div><br><div><div><span \
style="font-size: 13px; background-color: rgb(255, 255, 255); font-family: arial, \
sans-serif; ">-----</span></div><div><a href="https://twitter.com/FreddyMallet" \
style="font-family:arial,sans-serif;background-color:rgb(255,255,255)" \
target="_blank">twitter.com/FreddyMallet</a></div><div><span \
style="background-color:rgb(255,255,255)">Sonar for Continuous \
Inspection</span></div><br><br><br><div class="gmail_quote">On Tue, Feb 28, 2012 at \
1:07 AM, Scott Wolk <span dir="ltr"><<a \
href="mailto:swolk@netbase.com">swolk@netbase.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div \
style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div><div><div><div><div><div><div><span>Hi \
there, we want to switch from clover code coverage to jacoco.
There is a couple of projects that exclude classes from code coverage,
but we still run rules on them for violations. I tried using
sonar.jacoco.excludes but instead of excluding that code for
coverage, it just assigns 0% to them so that it lowers the coverage
numbers for their components. I can't understand the logic of this.
Shouldn't it exclude those classes from instrumentation AND the coverage
report like clover and cobertura excludes? It would be great to
change this behavior instead of waiting for SONAR-766 to be \
addressed. </span></div><div><span><br>Thanks,</span></div></div></div><div><span>Scott</span></div></div><div><form \
method="post" action="http://spam.gmane.org/gmane.comp.java.sonar.general:15251:unconfirmed" \
target="_blank" onsubmit="return window.confirm("You are submitting information \
to an external page.\nAre you \
sure?");"><br></form></div></div></div></div></div></blockquote></div><br></div></div></span></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic