-
Suggestion
-
Resolution: Duplicate
-
None
This is to avoid the need for the 10M clover.jar to be on the classpath of an application at rumtime.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CLOV-563] Make a single minimal Clover runtime jar that only includes classes required by running instrumented applications.
We build a large desktop application delivered through Java Webstart (JWS). We run a Bamboo instance that continuously builds the application. As part of the continuous build we have a suite of automated tests that run at the user level via JWS using QFTest from QFS. We gather coverage for the entire application using Clover. A 10MB jar slows the process (as JWS downloads the whole thing after each build).
The clover runtime jar in customer war files, or its contents in customer jar files. There's nothing wrong with having a 10m jar on the classpath, classes are loaded on demand. If we cause our customers jars or wars to be inflated then it tends not look so good.
Not 100% clear we need to pare it down. I.e. is 10m really a problem? It may make their dev cycle a bit slower if its unzipped on every web app launch.
Having a 10m jar is fine. It's when we force our customers to include a 10m jar worth of classes that it becomes less than fine.
Update:
CLOV-1238is implemented, will be published with Clover 4.0.6. In the meantime you can download clover-runtime-4.0.6-SNAPSHOT.jar from maven.atlassian.com.