Comment 1 Bela Bara 2015-12-01 04:40:27 EST

Which internal API is used?

Comment 2 Alexandra Schladebeck 2015-12-01 04:43:43 EST

Assigning to Markus for him to provide information on which internal API is used so that Bela can see whether it can be changed.

Comment 3 Markus Tiede 2015-12-02 03:29:24 EST

The usage is within the "com.bredexsw.jubula.core/com.bredexsw.guidancer.autagent.monitoring.jacoco/src/" src-project folder in package "com.bredexsw.guidancer.autagent.monitoring.jacoco".

Both classes located there import at least one internal JaCoCo class:
 - org.jacoco.core.internal.analysis.BundleCoverageImpl
 - org.jacoco.core.internal.analysis.SourceFileCoverageImpl

Comment 4 Bela Bara 2015-12-03 02:30:04 EST

There is no public API, which contains the related classes. We should ask to move these classes to public API.

Comment 5 Bela Bara 2015-12-07 09:38:37 EST

https://github.com/jacoco/eclemma/issues/111

Comment 6 Bela Bara 2016-01-13 07:54:51 EST

Cause of we have a custom CoverageBuilder (reason is managing multiple package patterns and class file id collision), we could use public factory methods in our CoverageBuilder,to avoid the usage of internal API.

Comment 7 Alexandra Schladebeck 2016-01-14 06:36:01 EST

Bela, does that mean that we can make some changes to resolve this?

Comment 8 Bela Bara 2016-01-14 06:44:44 EST

If we got published the corresponding factory methods in a new JaCoCO version, probably we can resolve it by using that methods.

Comment 9 Alexandra Schladebeck 2016-01-22 06:50:22 EST

So there's nothing we can do at the moment.

Comment 10 Oliver Goetz 2016-02-02 02:03:53 EST

Closed due to comment 9