Solves issue #51

[stephanenicolas]

Solves issue #51
I made all changes. Now tasks are created per variant (e.g. unMockDebugUnitTest, unmockMyBuildTypeReleaseUnitTest, etc.).

There is no afterEvaluate block anymore.

And cherry on top of the cake, as the plugin is in Groovy, it benefits from a full dynamic typing and doesn't rely on the android plugin ;) . But honnestly it would be better to have it typed, in kotlin, and depending on the plugin IMHO.

[stephanenicolas]

@drewhannay thx for the comment ! I just pushed a commit to fix it, the change is a few lines above your comment.

[drewhannay]

LGTM! FYI one of us will have to update our PR, depending on who gets merged first :)

[stephanenicolas]

Thx for the review @drewhannay . @bjoernQ we're quite ready :)

[bjoernQ]

@stephanenicolas just merged the other PR - this one needs an update now unfortunately

[stephanenicolas]

@drewhannay @bjoernQ here is the new PR. I changed quite a few things from my previous PR and actually re-ordered a few things in the plugin to take into account the lazy configurations and the tests variants.

Now things are more clear:

• we create a unique configuration with a default dependency to android jar
• we create a unique task to unmock for all variants, the task uses the unique configuration
• we create a unique dependency for all tests variants
• this dependency is provided by the unique task: when gradle will need it, it will run the task, prior to compilation
• all test variants compile task use the dependency (because it's test implementation).
• as a safe guard I also made each test variants compile task depend on the unique task

[drewhannay]

LGTM :)