RE: [jira] Commented: (LUCENE-1769) Fix wrong clover analysis because of backwards-tests, upgrade clover to 2.4.3 or better

This is correct but still inefficient. The current workflow is:
- Checkout svn
- Build the source package with ant
- Build the maven artifacts (which compiles all classes)
- Then ant nightly is called, which builds the binary package and runs tests
-> this could be optimized to only build the binary package
- ant clean 
- ant nightly with clover enabled -> This packages the binaries again, but
does not copy them. This is also not the best. This step should simple do
ant test with clover
- build the clover report

I only want to remove the call to the (I call it deprecated "nightly"
target, which is a relict from the time before Hudson and replace by
"package" in the first run and to "ant test" for the clover enabled version.
The build would run two times faster.

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@xxxxxxxxxxx


> -----Original Message-----
> From: Chris Hostetter [mailto:hossman_lucene@xxxxxxxxx]
> Sent: Friday, July 31, 2009 8:07 PM
> To: java-dev@xxxxxxxxxxxxxxxxx
> Subject: Re: [jira] Commented: (LUCENE-1769) Fix wrong clover analysis
> because of backwards-tests, upgrade clover to 2.4.3 or better
> 
> 
> : I didn't realize the nightly build runs the tests twice (with & w/o
> : clover); I agree, running only with clover seems fine?
> 
> i'm not caught up on this issue, but i happen to notice this comment in
> email.
> 
> the reason the tests are run twice is because in between the two runs we
> package up the jars.  clover instruments all the classes, so if we only
> ran hte tests once (w/clover), and then packaged the jars the nightly
> builds would include clover instrumented bytecode.
> 
> if you look at the old Jira issues about clover this is discussed there.
> 
> 
> 
> -Hoss
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@xxxxxxxxxxxxxxxxx
> For additional commands, e-mail: java-dev-help@xxxxxxxxxxxxxxxxx



---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: java-dev-help@xxxxxxxxxxxxxxxxx