Emma instrumentation does not work when Proguard is enabled

[deadmoto]

The problem is in lifecycle bindings themselves.
Proguard is bind to process classes phase but Emma is bind to prepare package phase.
When both Emma and Proguard are enabled, plugin builds project in the following order:

1. Compile classes and put into target/classes
2. Run Proguard and put obfuscated/optimized classes into something_obfuscated.jar (depends on plugin version).
3. Instrument classes in target/classes with Emma instrumentation
4. Pack something_obfuscated.jar into DEX file

This way instrumented classes just won't get into DEX and you will get 37 bytes coverage.ec file which basically means it is empty.

To fix the problem it is possible to re-bind emma goal to process classes phase:

<executions>
    <execution>
        <id>default-emma</id>
        <phase>process-classes</phase>
    </execution>
</executions>

Problem exists in android-maven-plugin for a long time and I observed it in 3.6.0 and 3.9.0-rc.2.

[mosabua]

If you got a fix... we would take it.

[mosabua]

Can you submit a pull request?

[deadmoto]

I am sorry for so long delay, I had a fix but I had no enough time to test it in real world.
I was unable to attach pull request to this issue directly so I have sent is as a regular pull request.
However I mentioned this issue in commit message so it must be referenced once approved.

[mosabua]

Where did this go?

[mosabua]

Closing old issue as cleanup