Hello there, my eclipse workspace contains about 15 projects; and all of them I need basically to be open. Those projects contain insane amounts of code ... which of course, ofr anything I do, only 0.0001% are of interest.
In other words: a) I have some production project P, that contains ONE package x.y.z b) I have some test project P-test, that contains ONE package x.y.z Now I want to run the JUnit test in P-test x.y.z; and afterwards I want eclemma to show me coverage ... only for the classes from P x.y.z (and of course, the main thing is that I want eclemma to only compute coverage for that one package; and to ignore anything else). I thought this would be thing that everybody does everyday, but the FAQ and the user guide ... gave me ideas ... which didn't help. No matter what I do, eclemma sits there for 2 minutes, computing coverage for ALL stuff in my workspace. And other people seem have the same problems: http://stackoverflow.com/questions/14448603/how-do-i-ignore-scanning-certain-classes-using-eclemma-and-eclipse Long story short: how can I make sure that eclemma isn't spending 2 minutes to compute 0% coverage for millions of LOC I am not interested in at all? Regards, eg -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/c272a4ea-ef2a-46fe-b379-d2d57a778729%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
