> A very stupid problem, but after a long time sitting in fornt of the 
> build.xml I
> found it:
> 
> 1. The biggest problem was: the target "clover" was made in a way that it used
> the clover.loaded sysprop to avoid permgen issues. Unfortunatley it not only
> loaded clover, it also set it up in this task (setting the java source file 
> folders). If
> the taskdef was then loaded for the first time, it had its source folders set 
> up
> with the module it was called first. The later coming compilation of another
> module did not run clover.setup anymore, so no new source folders were
> configured. I split up the IVY-Load+Taskdef from the clover setup
> 
> 2. test-framework had a strange comment that it should not depend on clover,
> which I removed. This was done to disable instrumentation for test-framework
> at all. I fixed this to make the test-framework's sources to be "defined" as 
> "test-
> sources" not application class, so clover is enabled but it's now handled as 
> tests
> (this was done by redefinition of -clover.setup task in test-framework). Same
> for Solr.

This did not work, so I disabled instrumentation for the test-framework again 
(Lucene+Solr), but with a better approach (overriding -clover.setup target by 
an empty one).

> I will play around a little longer and then commit.

I opened an issue and attached patch.
https://issues.apache.org/jira/browse/LUCENE-4445

> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
> 
> 
> > -----Original Message-----
> > From: Robert Muir [mailto:[email protected]]
> > Sent: Friday, September 28, 2012 2:50 AM
> > To: [email protected]
> > Subject: clover report incomplete?
> >
> > https://builds.apache.org/job/Lucene-Solr-Clover-4.x/clover/pkg-summar
> > y.html
> >
> > doesn't seem to include any of the packages in codecs/ module (e.g.
> > appending, block, ...)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected] For
> > additional commands, e-mail: [email protected]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to