You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2022. It is now read-only.
Would it be possible to add a per project filter that includes only the selected packages and exclude everything else?
I am running code coverage on a NetBeans platform module that depends on quite a number of other (large) modules. And the coverage report takes around 30 minutes to generate because it looks at the large number of packages in the other modules too. I suspect this might be the real cause of issue number #29 too - it will complete eventually.
Is there maybe a manual workaround in the meantime, such as editing the project.json file somehow?
The text was updated successfully, but these errors were encountered:
I have found the manual workaround, after reading the plugin's source code.
To the project.properties file of the module, I added this line (of course with real package names): jacoco.excludes=za.co.nameofpackage.*:za.co.nameofsecondpackage.*
This helped a lot, the process now takes only 10 minutes. :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would it be possible to add a per project filter that includes only the selected packages and exclude everything else?
I am running code coverage on a NetBeans platform module that depends on quite a number of other (large) modules. And the coverage report takes around 30 minutes to generate because it looks at the large number of packages in the other modules too. I suspect this might be the real cause of issue number #29 too - it will complete eventually.
Is there maybe a manual workaround in the meantime, such as editing the project.json file somehow?
The text was updated successfully, but these errors were encountered: