If MBean registered by default, then what to do with an existing output mode "mbean" ? Possible options - fully drop it, or it will behave as "none".

Also should be noted that as mentioned in #61 package "javax.management" not available on Android.
And BTW package "java.lang.instrument" also not available on Android, which is not fatal, but leads to messages in log like:

W/ClassPathPackageInfoSource(  775): java.lang.ClassNotFoundException: org.jacoco.agent.rt.CoverageTransformer
W/ClassPathPackageInfoSource(  775):    at java.lang.Class.classForName(Native Method)
W/ClassPathPackageInfoSource(  775):    at java.lang.Class.forName(Class.java:217)
W/ClassPathPackageInfoSource(  775):    at android.test.ClassPathPackageInfoSource.createPackageInfo(ClassPathPackageInfoSource.java:88)

And I don't know how to suppress those messages without removal of classes.

I don't think mbean output is widely used, so we can drop this and clearly document this in the change log. On the other hand if enable it by default this might cause issues in some scenarios. So maybe the default should be no JMX.

Regarding missing APIs on Android the only solution is probably a different JaCoCo runtime packaging without JMX and Java agent support. As the error log is not a show stopper I wouldn't try to solve this right now.

@Godin Hi Evgeny, can you please verify that this version also works on Android? I'm asking because the current implementation has direct javax.management references from the Agent class. If this causes problems I we need to pull JMX operations into a separate class (like MBeanController was before).

@Godin Thanks for reviewing, I fixed the typos. Good to merge?

@marchof I'll test on Android tomorrow morning and will come back to you about merge.

@marchof It works fine on Android, since the code to create MBean (i.e. which uses non-existent package) not executed by default. So we can safely merge this!