Why not execute Gradle with debug information and watch what it will print?
Most likely message will be
Writing bundle 'ProjectName' with 0 classes
Because such report is likely due to absence of classes to analyze, i.e. in
classDirectories = subprojects.sourceSets.main.output
--
You
Hi Christian,
you might try offline instrumentation for the class files.
If you’re adding your own class loaders you might also consider doing
on-the-fly instrumentation within your class loaders. See our API example
“CoreTutorial”: https://www.jacoco.org/jacoco/trunk/doc/api.html
Hi Evgeny,
thanks for the quick reply.
you wrote:
> On Friday, December 14, 2018 at 11:38:35 AM UTC+1, Andreas Sewe wrote:
> is it possible at the moment to include the test sources/classes in the
> reported generated by jacoco-maven-plugin:report?
>
>
> No, it is not possible with
Hi Andreas,
On Friday, December 14, 2018 at 11:38:35 AM UTC+1, Andreas Sewe wrote:
>
> Hi all,
>
> is it possible at the moment to include the test sources/classes in the
> reported generated by jacoco-maven-plugin:report?
>
No, it is not possible with jacoco-maven-plugin:report
> AFAICT
On Thursday, December 13, 2018 at 4:57:38 PM UTC+1,
ashfaqur.rahm...@gmail.com wrote:
>
> Workaround will not work since the jacoco plugin is looking for the
> classes of code under test also under each project directory (afaik)
> in-order to generate the report.
Location of classes doesn't
Hi JaCoCo team,
I'm writing a JUnit 5 support library that isolates main/test/others classes
into dedicated class loaders. The first client of that library will be a Maven
Plugin similar to Surefire. As I want to support "code coverage" early I'm
thinking about ways how to enable this feature
On Friday, December 14, 2018 at 3:08:08 PM UTC+1, Andreas Sewe wrote:
>
> Hi Evgeny,
>
> thanks for the quick reply.
>
> you wrote:
> > On Friday, December 14, 2018 at 11:38:35 AM UTC+1, Andreas Sewe wrote:
> > is it possible at the moment to include the test sources/classes in
> the
>
I agree with Evgeny. There is another important requirement in many build
setups:
You might want to use a different JDK for running your tests (e.g. when running
your test suites against latest JDKs).
Cheers,
-marc
> On 14. Dec 2018, at 16:28, Evgeny Mandrikov wrote:
>
> While you can do
On Friday, December 14, 2018 at 3:34:05 PM UTC+1, Andreas Sewe wrote:
>
> Evgeny Mandrikov wrote:
> > Ticket already exists - https://github.com/jacoco/jacoco/issues/271
>
> Good to know.
>
> Given that the PR is from 2015, is there anything I can do to speed this
> along, e.g., only
On Friday, December 14, 2018 at 2:51:12 PM UTC+1, Marc R. Hoffmann wrote:
> Hi Christian,
>
>
> you might try offline instrumentation for the class files.
>
>
> If you’re adding your own class loaders you might also consider doing
> on-the-fly instrumentation within your class loaders. See
Evgeny Mandrikov wrote:
> Ticket already exists - https://github.com/jacoco/jacoco/issues/271
Good to know.
Given that the PR is from 2015, is there anything I can do to speed this
along, e.g., only introducing without the (distinct)
report selection feature? For example, creating another PR?
While you can do what Marc proposed,
recommended way of JaCoCo usage/integration - is agent,
mainly because of its simplicity in understanding by end-users,
especially compared to ClassLoaders.
Moreover
On Friday, December 14, 2018 at 2:16:06 PM UTC+1, sormu...@gmail.com wrote:
>
> At the
12 matches
Mail list logo
