Marc R. Hoffmann
Marc R. Hoffmann
Hi @the-end-sea-of-the-world, welcome to the JaCoCo project and thanks for your contribution! We try to provide a regression test for every feature. What about adding (or extending) the [existing tests](https://github.com/jacoco/jacoco/blob/master/org.jacoco.cli.test/src/org/jacoco/cli/internal/commands/ReportTest.java)...
@the-end-sea-of-the-world thanks for the update! To be honest I don't think we will maintain the demo code in the JaCoCo project. May I ask you to remove it?
Also as you can see [here](https://github.com/jacoco/jacoco/pull/1303/checks) the build fails as the source code has some formatting issues. Our development setup with Eclipse auto-formatting is described [here](https://www.jacoco.org/jacoco/trunk/doc/environment.html).
Dear @soufianenassih , can you please explain your use case for "a large list of excludes class names"?
@soufianenassih I rephrase my question: **Why** do you need to exclude classes?
@soufianenassih Then you only need to specify the exclude list when you create the report. No need to exclude classes for the agent.
So in this case I close this PR.
@soufianenassih To manage expectations: We're very reluctant with adding new config options as they complicate reproducing/debugging error reports. Also all down-stream tools have to be considered (Maven, Ant, Gradle etc)....
Can you change the name of the generated classes and give it a common Prefix, e.g. `Generated$`?
And what about my other question: What exact problem is caused by JaCoCo instrumentation? Maybe this problem can be prevented.