Emma coverage was not applied to apklib or aar projects. Now it is #689
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@mosabua Is there anything you need for reviewing/merging this? |
|
Time ... ;-) More seriously.. I am working through all the PRs towards a new release now. |
mosabua
added a commit
that referenced
this pull request
Jan 19, 2016
Emma coverage was not applied to apklib or aar projects. Now it is
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I followed the instructions at : http://simpligility.github.io/android-maven-plugin/emma.html I noticed that my coverage.em file was not being generated in my library module but it was in my test module. I did some sleuthing and noticed the emma mojo wan't included for the aar packaging type. I've updated this in the components file and have code coverage for my projects.