class files are not stored inside exec-file,
location of class files used by IDE
can be different
from location of class files used by Gradle build,
and is actually different as shown on below screenshot,
And once again:
since you have trouble with generation of report using Gradle task, then
you must debug Gradle task instead of focusing on IDE,
and one of the ways to start doing this - is to execute Gradle with more
verbose log ("gradle --info" or "gradle --debug") and watch what will be
printed during execution of your task.
[image: screenshot.png]
On Monday, December 17, 2018 at 3:42:39 PM UTC+1, Balesh koijam wrote:
>
> Thanks Mandrikov for the reply,
>
> as mentioned above, the exec file that was generated was used to generate
> the coverage report using the Intellji feature, where i could see the
> reports looking good. with this , i am assuming that classes should be
> there to analyze. please correct me if my understanding is wrong.
>
>
>
> On Friday, 14 December 2018 07:55:16 UTC-5, Evgeny Mandrikov wrote:
>>
>> 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 received this message because you are subscribed to the Google Groups
"JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/27094608-d0b7-4926-a056-d31bdfbdbf5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
