RE: [Cobertura-devel] Multiple Source directories

[Seigel, J. <Jam...@av...>]

Hello all!

I have uploaded my changes to support filesets, some refactoring, and =
some unit testing to the sourceforge area under the patch id 1223838.  =
If you are interested (anyone) lease have a look and see how the =
implementation look and see how it performs on your codebase.  I have =
run this against some sample projects and it seems to be alright. =20

If this is used, then I am sure we could change the instrumentation =
target to accept multiple filesets as well.

cheers
James.


-----Original Message-----
From: Mark Doliner [mailto:Mar...@sa...]
Sent: Wed 6/15/2005 1:49 PM
To: Seigel, James
Cc: cob...@li...
Subject: RE: [Cobertura-devel] Multiple Source directories
=20
> Yes, sourcefiles should definitely be tied to a specific=20
> parent base directory.  Could we ret rid of the --basedir=20
> argument completely and specify directories and files as follows
>=20
> cobertura-instrument.bat --datafile C:\cobertura.ser=20
> C:\mysrcdir1 C:\mysrcdir2=20
> C:\mysrcdir3\com\example\meatballfactory=20
> C:\mysrcdir3\com\example\meatballconsumer C:\mysrcdir4

Hmm, I guess Cobertura needs a way to figure out which parts of =
"C:\mysrcdir3\com\example\meatballconsumer" are a part of the package =
name...

Could we maybe just have people specify source directories, and not have =
the ability to specify individual files?  For the reporting task it =
shouldn't matter if we specify .java files that aren't used, right?

Now the instrument task on the other hand, I think we'll definitely want =
a way for users to specify individual classes.  But for instrumenting, =
I'm not sure Cobertura needs to know the which parts of the file name =
are parts of the package name, I think it might be able to get that info =
from the .class file.

-Mark