Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: domain of peter.j.donald@gmail.com
 designates 209.85.213.52 as permitted sender)
MIME-Version: 1.0
Sender: peter.j.donald@gmail.com
In-Reply-To: <AEAF088B-DFB8-455E-BD9A-292D436068F4@pyxis-tech.com>
References: <6FDAB7E1-3205-49B7-BE99-64E4D5E89B92@pyxis-tech.com>
	<CACiKNc6f2D2CiYhRMni=mvokooULK_svgNvVNg-JtZA7cC0B9w@mail.gmail.com>
	<E1ECAE43-6C69-49B4-9875-FB8E591D01EC@pyxis-tech.com>
	<CAN=tixmcraPF955poMZ3Z5=xD5RWJKyjjeX2B-GzJbfYHYhpyg@mail.gmail.com>
	<8E312E5E-BB52-4F0A-B6E0-62FB994690B4@pyxis-tech.com>
	<CACiKNc5HJWodi2A7cTXWF-Dm+3fCyhCm1hkUav1aCw+uzmYH1g@mail.gmail.com>
	<AEAF088B-DFB8-455E-BD9A-292D436068F4@pyxis-tech.com>
Date: Fri, 25 Apr 2014 09:53:33 +1000
Message-ID: 
 <CACiKNc7_2o2awHPC7zHdc3Ec8xPXwv4w=OPy9cmz_2X1+Rwo7w@mail.gmail.com>
Subject: Re: Help with code coverage
From: Peter Donald <peter@realityforge.org>
To: users@buildr.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On Sat, Mar 29, 2014 at 12:19 AM, Vincent Tence <vtence@pyxis-tech.com> wro=
te:
> I think Tammo's version (https://github.com/apache/ode/blob/master/tasks/=
jacoco.rake) is a good starting point. It generates and aggregates reports =
in a multi-project build. Looking at the code, it defines a top-level jacoc=
o namespace with a report aggregation task that the official jacoco plugin =
seems to be missing.

True that. I just merged this functionality into the core buildr task.

> My problem right now is that I am unable to include the integration test =
run in the report. Whenever integration tests run, the aggregated report is=
 not generated.

I know this was ages ago but did this ever get sorted?

If not do the integration tests generate the .exec files in the
correct locations? Can you run it in --trace and see what parameters
are passed to the integration tests and if they include the jacoco
system properties.


> Eventually, I'd like to hack a plugin to integrate with coveralls.io, whi=
ch provides great online reports and stats for code coverage, is free for o=
pen-source projects and integrates well with GitHub.

That sounds like a good idea.

There was someone (?) a while back else who was doing this a while ago
to try and maintain state between TravisCI runs ... will see if I can
find the email.  I would like to see what ever you come up with.

--=20
Cheers,

Peter Donald