From: Mark D. <Mar...@sa...> - 2005-06-16 20:33:17
|
Cobertura currently consists of one jar file, and this jar must be on = your classpath when instrumenting, running tests, and reporting. = However, when you actually run your tests, only one of the packages in = this jar is used, and the package only requires log4j. How do people feel about creating a cobertura.jar and a = cobertura-runtime.jar, where cobertura-runtime.jar contains all the = classes in the package net.sourceforge.cobertura.coveragedata. And = cobertura.jar would contain everything else (ant tasks, instrumenting = code, reporting code, etc.) The goal is to make it more clear that asm, ncss, jakarta-oro, etc. are = not required when running instrumenting code. I think this would help = avoid classpath conflicts with ASM. Good idea? Bad idea? Suggestions for better names for the jars? = Should the jars include the version number in their name = ("cobertura-1.5.jar")? Should the runtime jar still use log4j, or = should we get rid of that dependency? FYI, I'll be out of town from now until Sunday night. -Mark |