cobertura-devel — General questions about using and developing Cobertura.

[Cobertura-devel] Direct download of Coberura 1.5 ?

[nicolas\.brault <nic...@la...>]

Hi,

Would it be possible to know when Cobertura 1.5 will be
available in direct download ?
I would like to use it but I can't access CVS.=0A=0AAcc=E9dez au courrier=
 =E9lectronique de La Poste : www.laposte.net ; =0A3615 LAPOSTENET (0,34=80=
/mn) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)=0A=0A

[Cobertura-devel] Possible reporting bug in CVS?

[Mark D. <Mar...@sa...>]

Does anyone have any ideas about what could be causing the following =
bug?  I suppose you could leave comments on how the person might go =
about debugging it, or maybe ask for more information, if it would help.

http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1251689&grou=
p_id=3D130558&atid=3D720015

-Mark

RE: [Cobertura-devel] Tests For FileFinder

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

Hey no worries.  I did something similar when I walked through the code
and added the fileset thing...

=20

The "other CCN" references in my other email, ignore that.  They are
covered off just nicely :D  I thought I saw one accessing files with out
the filefinder but nahh they are all good.

=20

Cheers

James.

=20

=20

________________________________

From: Jeremy Thomerson [mailto:jer...@gm...]=20
Sent: Wednesday, August 03, 2005 4:21 PM
To: Seigel, James
Cc: cob...@li...
Subject: Re: [Cobertura-devel] Tests For FileFinder

=20

Awesome!! I'll try to add them in tonight.  I just committed a change to
FileFinder that adds a finder method for finding directories (for
package finding).  This is used to compute CCN in HTMLReport.

Thanks again!
Jeremy

On 8/3/05, Seigel, James <Jam...@av...> wrote:

Hello All.

=20

I whipped up some simple tests for Filefinder and stuck them in the
patch area.  If you are interested, have at 'em.

=20

Cheers

James.

=20

---
James Seigel
Software Developer
Avocent Mobile Solutions
Direct: 403.355.2574
Toll Free: 866.602.2002

=20

=20

Re: [Cobertura-devel] Tests For FileFinder

[Jeremy T. <jer...@gm...>]

Awesome!! I'll try to add them in tonight. I just committed a change to=20
FileFinder that adds a finder method for finding directories (for package=
=20
finding). This is used to compute CCN in HTMLReport.

Thanks again!
Jeremy

On 8/3/05, Seigel, James <Jam...@av...> wrote:
>=20
>  Hello All.
>=20
>  I whipped up some simple tests for Filefinder and stuck them in the patc=
h=20
> area. If you are interested, have at 'em.
>=20
>  Cheers
>=20
> James.
>=20
>  ---
> James Seigel
> Software Developer
> Avocent Mobile Solutions
> Direct: 403.355.2574
> Toll Free: 866.602.2002
>=20
>

Re: [Cobertura-devel] Re: Cobertura 1.5

[Jeremy T. <jer...@gm...>]

WWVzLCBJIGxlZnQgdGhhdCBvdXQgYnkgYWNjaWRlbnQuIEkgZml4ZWQgaXQgYW5kIGFkZGVkIGEg
ZmluZERpcmVjdG9yeSAKbWV0aG9kIHRvIEZpbGVGaW5kZXIuIFRoYW5rcyBmb3IgY2F0Y2hpbmcg
dGhhdC4KCkkgd2Fzbid0IHN1cmUgd2hhdCB5b3UgbWVhbnQgYWJvdXQgRmlsZUZpbmRlciByZWZl
cmVuY2VzLiBBbnkgZXhhbXBsZXM/CgpUaGFua3MhCkplcmVteQoKT24gOC8zLzA1LCBTZWlnZWws
IEphbWVzIDxKYW1lcy5TZWlnZWxAYXZvY2VudC5jb20+IHdyb3RlOgo+IAo+ICBKZXJlbXksCj4g
Cj4gIERpZCB5b3UgbGVhdmUgb3V0IHNvbWUgQ0NOIGNhbGN1bGF0aW9ucyBpbiB5b3VyIGNoYW5n
ZXM/IEkgbm90aWNlZCBsaW5lIAo+IDY4OCBpbiBIdG1sUmVwb3J0IHNvbWUgY29tbWVudGVkIG91
dCBjY24gY2FsY3VsYXRpb25zLCBhbmQgaXQgbG9va3MgbGlrZSB5b3UgCj4gYXJlIG1pc3Npbmcg
c29tZSBmaWxlZmluZGVyIHJlZmVyZW5jZXMgaW4gdGhlcmWFYnV0IEkgY291bGQgYmUgd3Jvbmcg
OkQKPiAKPiAgQ2hlZXJzCj4gCj4gSgo+IAo+ICAgICAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0KPiAgCj4gKkZyb206KiBjb2JlcnR1cmEtZGV2ZWwtYWRtaW5AbGlzdHMuc291cmNlZm9y
Z2UubmV0IFttYWlsdG86Cj4gY29iZXJ0dXJhLWRldmVsLWFkbWluQGxpc3RzLnNvdXJjZWZvcmdl
Lm5ldF0gKk9uIEJlaGFsZiBPZiAqSmVyZW15IAo+IFRob21lcnNvbgo+ICpTZW50OiogVHVlc2Rh
eSwgQXVndXN0IDAyLCAyMDA1IDExOjM5IFBNCj4gKlRvOiogR3J6ZWdvcnogTHVrYXNpawo+ICpD
YzoqIGNvYmVydHVyYS1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKPiAqU3ViamVjdDoqIFJl
OiBbQ29iZXJ0dXJhLWRldmVsXSBSZTogQ29iZXJ0dXJhIDEuNQo+ICAKPiAgT2theSwgYWxsIHRo
ZSBjaGFuZ2VzIGFyZSBjb21taXR0ZWQgZm9yIHRoZSBmaWxlc2V0cyBjaGFuZ2VzLiBHcnplZ29y
eiwgSSAKPiBjb3VsZG4ndCBhZGQgeW91ciBjaGFuZ2VzLCBJJ2xsIGxldCB5b3UuIEkgcmVhbGx5
IHdhbnRlZCB0bywgYnV0IHRoZXJlIHdlcmUgCj4gc28gbWFueSBvdGhlciBjaGFuZ2VzLCBpdCBt
YWRlIGl0IGRhdW50aW5nLiAKPiAgCj4gICBPbmUgdGhpbmcgdG8gbm90ZTogTWFyayBjb21taXR0
ZWQgc29tZSBjaGFuZ2VzIHRvZGF5IHRoYXQgd2VyZSBmcm9tIAo+IHZhcmlvdXMgcGF0Y2hlcywg
YW5kIEkgaGFkIHRvIG1hbnVhbGx5IG1lcmdlIGEgY291cGxlIG9mIGZpbGVzIGJlY2F1c2UgdGhl
cmUgCj4gd2VyZSBzbyBtYW55IGNvbmZsaWN0aW5nIGNoYW5nZXMgaW4gdGhlIHNhbWUgY2xhc3Mg
KHNpbmNlIEkgcHJldHR5IG11Y2ggCj4gZW50aXJlbHkgcmV3cm90ZSBhIGNvdXBsZSBvZiBjbGFz
c2VzKS4gVGhlIG9ubHkgb25lIHRoYXQgSSdtIGNvbmNlcm5lZCBhYm91dCAKPiBpcyBpbnN0cnVt
ZW50aW5nL01haW4uamF2YS4gSSB0aGluayB0aGF0IGNhbWUgZnJvbSBHcnplZ29yeidzIHBhdGNo
IGlmIEknbSAKPiBub3QgbWlzdGFrZW4uIEkgdGhpbmsgSSBnb3QgZXZlcnl0aGluZywgYnV0IGNv
dWxkIHlvdSBqdXN0IGNoZWNrIHRvIG1ha2UgCj4gc3VyZT8gSXQgbG9va2VkIGxpa2UgbW9zdCBv
ZiB5b3VyIGNoYW5nZXMgaW4gaXQgcmV2b2x2ZWQgYXJvdW5kIHJlZ2V4ZXMgCj4gYmVpbmcgYSBD
b2xsZWN0aW9uIHJhdGhlciB0aGFuIGEgUGF0dGVybiwgYnV0IEkgaGFkIHNvIG1hbnkgY2hhbmdl
cyBpbiB0aGF0IAo+IGNsYXNzIGl0IHdhcyBoYXJkIHRvIHRlbGwuIAo+ICAKPiAgIElmIEkgbWVz
c2VkIGFueW9uZSdzIHBhdGNoIHVwLCBJIGFtIHNpbmNlcmVseSBzb3JyeS4gSSdsbCBvd2UgeW91
IGEgCj4gYmVlciwgYW5kIEknbGwgZG8gYW55dGhpbmcgSSBjYW4gdG8gaGVscCB5b3UgZ2V0IGl0
IGJhY2sgdG8gd2hhdCB5b3UgaGFkIAo+IHN1Ym1pdHRlZC4KPiAgCj4gICBUaGFua3MgdG8gZXZl
cnlvbmUhIFBsZWFzZSB0ZXN0IHRoaXMgKHdpdGggbXVsdGlwbGUgc291cmNlIGRpcmVjdG9yaWVz
KSAKPiBhbmQgbGV0IG1lIGtub3cgaWYgeW91IGZpbmQgYW55dGhpbmcgdGhhdCBuZWVkcyB0byBi
ZSBsb29rZWQgYXQuIElmIHlvdSBwdWxsIAo+IGRvd24gdGhlIGxhdGVzdCBjb2RlIGZyb20gQ1ZT
IGFuZCBkbyBhIGJ1aWxkLCBpdCBpbmNsdWRlcyB0aGUgbXVsdGlwbGUgCj4gZGlyZWN0b3JpZXMg
c28gd2UgY2FuIHNlZSBpdCB3b3JrLiAKPiAgCj4gICBUaGUgb25seSByZWdyZXR0YWJsZSB0aGlu
ZyB0aGF0IHRoaXMgY29tbWl0IGRpZCBpcyBjb21tZW50ZWQgb3V0IG91ciAKPiBYTUxSZXBvcnRU
ZXN0LiBJIGRpZG4ndCBoYXZlIHRpbWUgdG8gbG9vayBpbnRvIHdoYXQgaXQgd291bGQgdGFrZSB0
byBzd2l0Y2ggCj4gaXQgdG8gYmUgb3BlcmFibGUgd2l0aCB0aGUgY3VycmVudCBSZXBvcnRUYXNr
LiBJdCBsb29rZWQgbGlrZSBpdCB3YXMgcGFzc2luZyAKPiBpbiBjb21tYW5kIGxpbmUgYXJndW1l
bnRzLCB3aGljaCBoYXMgbm93IGNoYW5nZWQgdG8gYSBjb21tYW5kIGZpbGUsIGFuZCBpdCAKPiB3
YXMganVzdCB0b28gbXVjaCBmb3IgcmlnaHQgdGhlbi4gSWYgc29tZW9uZSB3YW50IHRvIGNvbnZl
cnQgaXQgKGFuZCB3cml0ZSAKPiBhbnkgb3RoZXIgdW5pdCB0ZXN0cyBmb3IgdGhlIG11bHRpLWZp
bGVzZXRzKSwgdGhhdCB3b3VsZCBiZSBncmVhdC4gCj4gIAo+ICAgSlQKPiAKPgo=

[Cobertura-devel] Tests For FileFinder

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

Hello All.

=20

I whipped up some simple tests for Filefinder and stuck them in the
patch area.  If you are interested, have at 'em.

=20

Cheers

James.

=20

---
James Seigel
Software Developer
Avocent Mobile Solutions
Direct: 403.355.2574
Toll Free: 866.602.2002

=20

RE: [Cobertura-devel] Re: Cobertura 1.5

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

Jeremy,

=20

Did you leave out some CCN calculations in your changes?  I noticed line
688 in HtmlReport some commented out ccn calculations, and it looks like
you are missing some filefinder references in there...but I could be
wrong :D

=20

Cheers

J

=20

=20

=20

________________________________

From: cob...@li...
[mailto:cob...@li...] On Behalf Of Jeremy
Thomerson
Sent: Tuesday, August 02, 2005 11:39 PM
To: Grzegorz Lukasik
Cc: cob...@li...
Subject: Re: [Cobertura-devel] Re: Cobertura 1.5

=20

Okay, all the changes are committed for the filesets changes.  Grzegorz,
I couldn't add your changes, I'll let you.  I really wanted to, but
there were so many other changes, it made it daunting. =20

=20

One thing to note:  Mark committed some changes today that were from
various patches, and I had to manually merge a couple of files because
there were so many conflicting changes in the same class (since I pretty
much entirely rewrote a couple of classes).  The only one that I'm
concerned about is instrumenting/Main.java.  I think that came from
Grzegorz's patch if I'm not mistaken.  I think I got everything, but
could you just check to make sure?  It looked like most of your changes
in it revolved around regexes being a Collection rather than a Pattern,
but I had so many changes in that class it was hard to tell.=20

=20

If I messed anyone's patch up, I am sincerely sorry.  I'll owe you a
beer, and I'll do anything I can to help you get it back to what you had
submitted.

=20

Thanks to everyone!  Please test this (with multiple source directories)
and let me know if you find anything that needs to be looked at.  If you
pull down the latest code from CVS and do a build, it includes the
multiple directories so we can see it work.=20

=20

The only regrettable thing that this commit did is commented out our
XMLReportTest.  I didn't have time to look into what it would take to
switch it to be operable with the current ReportTask.  It looked like it
was passing in command line arguments, which has now changed to a
command file, and it was just too much for right then.  If someone want
to convert it (and write any other unit tests for the multi-filesets),
that would be great. =20

=20

JT



=20

RE: [Cobertura-devel] Re: Cobertura 1.5

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

I will take a look at the code base and see if I can wedge any unit
tests in there and see what can be done with xmlreporttest

=20

Cheers

James.

=20

________________________________

From: cob...@li...
[mailto:cob...@li...] On Behalf Of Jeremy
Thomerson
Sent: Tuesday, August 02, 2005 11:39 PM
To: Grzegorz Lukasik
Cc: cob...@li...
Subject: Re: [Cobertura-devel] Re: Cobertura 1.5

=20

Okay, all the changes are committed for the filesets changes.  Grzegorz,
I couldn't add your changes, I'll let you.  I really wanted to, but
there were so many other changes, it made it daunting. =20

=20

One thing to note:  Mark committed some changes today that were from
various patches, and I had to manually merge a couple of files because
there were so many conflicting changes in the same class (since I pretty
much entirely rewrote a couple of classes).  The only one that I'm
concerned about is instrumenting/Main.java.  I think that came from
Grzegorz's patch if I'm not mistaken.  I think I got everything, but
could you just check to make sure?  It looked like most of your changes
in it revolved around regexes being a Collection rather than a Pattern,
but I had so many changes in that class it was hard to tell.=20

=20

If I messed anyone's patch up, I am sincerely sorry.  I'll owe you a
beer, and I'll do anything I can to help you get it back to what you had
submitted.

=20

Thanks to everyone!  Please test this (with multiple source directories)
and let me know if you find anything that needs to be looked at.  If you
pull down the latest code from CVS and do a build, it includes the
multiple directories so we can see it work.=20

=20

The only regrettable thing that this commit did is commented out our
XMLReportTest.  I didn't have time to look into what it would take to
switch it to be operable with the current ReportTask.  It looked like it
was passing in command line arguments, which has now changed to a
command file, and it was just too much for right then.  If someone want
to convert it (and write any other unit tests for the multi-filesets),
that would be great. =20

=20

JT

=20

On 8/2/05, Grzegorz Lukasik <ha...@gm...> wrote:=20

Jeremy,

I think there are two things from my patch that are easy to reuse in
yours. The first is CommandLineBuilder - it puts building-parsing long=20
command lines in one place. The second is ability of FileStore (yours
FileFinder) to compute complexity. Basically it removes complexity
computation from report classes, and computes complexity exactly for
files the report is generated for, and at most once for each one. Add=20
them to your patch if you like. I will add patches later, if you do
not want to complicate your solution now.

Grzegorz

On 8/1/05, Jeremy Thomerson <jer...@gm... > wrote:
> 1. okay, cool
>  2. agreed - will change
>  3. oops, you're right, it was for reference, forgot to remove
>  4. yeah, i'll remove the jar, too (i think that's the only dependency
--=20
> i'll check
>  5. i'll look to see where I did it -- not sure, but probably b/c my
default
> code template adds a default no-op constructor (something we do at
work, so
> the settings / habits carry over)=20
>  6. great suggestions - the kind of things I would normally do, not
sure why
> I didn't on this one
>  7. I'll add an assert so that we don't get any [potential] JUnit
> warnings.... even though the main point of the test is a no-op, it's
just to=20
> call methods
>
>  I'll look at his patch, too.  I did all of this development offline
> Saturday, so Saturday morning before I left the house, I saved the
fr's and
> bugs from SF to a text file, but forgot to grab the patches to use as=20
> reference / starting point.  Sorry to those of you who submitted
patches
> that I forgot to grab.  I will look at them before committing, though,
and
> merge anything that they include and I forgot.
>
>  Once I get these things done, I'll commit unless anyone objects
before
> that....
>
>  Until then,
>  Jeremy
>
>
> On 8/1/05, Mark Doliner < Mar...@sa...
<mailto:Mar...@sa...> > wrote:
> > I'll number things for reference:
> >
> > 1. I just committed the ChangeLog typo fix to get it out of the way,
> thanks for catching that.
> >=20
> > 2. It might be better if "othersrc" was called "src2," instead.
That way
> it would show up next to "src" in directory listings and people would
notice
> it more.  It also allows for us to have "src3" and higher (I doubt
that'll=20
> ever happen... but who knows).
> >
> > 3. You have a lot of code commented out in reporting.Main... It
looks like
> most of it was replaced with other code, and I guess you were using it
for=20
> reference, but I would definitely remove it before committing (if
people
> want to see an older version of the code then they can check out an
old
> revision from CVS).
> >
> > 4. I like that you stopped using gnu.getopt in reporting.Main.
Getopt is
> kind of overkill, I think, and I'd like to remove that jar.
> >
> > 5. Is there any reason you're adding empty constructors
ocassionally?
> I've just been implicitly using the default/parent's constructor.=20
> >
> > 6. In FileFinder.findFile you convert forward slashes to
backslashes... It
> seems like it would make more sense to do that in addSourceFilePath()
> instead.  And also to create a String filePartReplaced or something
before=20
> the loop in findFile instead of doing the search/replace for every
> iteration.  And I'd also vote for converting back slashes to forward
> slashes, but I'm a Linux guy :-)
> >
> > 7. Your faux TestCase for SomeOtherClass doesn't have an assert, it
seems=20
> like JUnit might warn against that?
> >
> > You might want to work with Grzegorz Lukasik or see if he does
anything in
> his patch that you might want to do in yours:
> >
>
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1245454&grou=
p_i
d=3D130558&atid=3D720017=20
> >
> > -Mark
> >
> >
> > > -----Original Message-----
> > > From: cob...@li...=20
> > > [mailto: cob...@li...]
> On
> > > Behalf Of Jeremy Thomerson
> > > Sent: Saturday, July 30, 2005 10:26 PM=20
> > > To: Mark Doliner
> > > Cc: cob...@li...
> > > Subject: [Cobertura-devel] Re: Cobertura 1.5
> > >
> > > I spent a few hours today making instrumentation and reporting
work
> > > with multiple source directories.  Rather than committing it, I am
> > > sending out the patch, asking for someone to review it.  It also
adds=20
> > > a second directory of source (just one simple faux class) so that
we
> > > have the multiple filesets / multiple source directories in our
> > > instrumentation and reporting build.=20
> > >
> > > I didn't have time to update any documentation that we have for
usage,
> > > so if someone could update that (assuming that everyone likes this
> > > solution), that would be great.  Also, I just realized that the=20
> > > reporting task should be backwards-compatible with the old srcdir
> > > attribute, but I don't think I remembered to do that with the
> > > instrumentation task.  If I didn't, but everyone likes this patch,

> > > I'll commit these changes and add that to the instrumentation
class
> > > for backwards compatibility.
> > >
> > > Please let me know what you think.
> > >=20
> > > Jeremy Thomerson
> > >
> > > On 7/27/05, M C < mor...@ya...> wrote:
> > > > Mark Doliner wrote:
> > > > >Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > > >It still doesn't supported multiple source
> > > > directories >for reporting (I REALLY need to look at
> > > > that patch), >or multiple class directories for=20
> > > > instrumenting, but >there are a lot of other changes.
> > > > >What do you guys think?
> > > >
> > > > IMHO Without the patch for multiple source directories=20
> > > > I personally do not see the point of a release now.
> > > > Better to wait for the real thing.
> > > >
> > > > Cheers,
> > > > Morten
> >
> >
> >
>
>



=20

Re: [Cobertura-devel] Re: Cobertura 1.5

[Jeremy T. <jer...@gm...>]

Okay, all the changes are committed for the filesets changes. Grzegorz, I=
=20
couldn't add your changes, I'll let you. I really wanted to, but there were=
=20
so many other changes, it made it daunting.=20
 One thing to note: Mark committed some changes today that were from variou=
s=20
patches, and I had to manually merge a couple of files because there were s=
o=20
many conflicting changes in the same class (since I pretty much entirely=20
rewrote a couple of classes). The only one that I'm concerned about is=20
instrumenting/Main.java. I think that came from Grzegorz's patch if I'm not=
=20
mistaken. I think I got everything, but could you just check to make sure?=
=20
It looked like most of your changes in it revolved around regexes being a=
=20
Collection rather than a Pattern, but I had so many changes in that class i=
t=20
was hard to tell.
 If I messed anyone's patch up, I am sincerely sorry. I'll owe you a beer,=
=20
and I'll do anything I can to help you get it back to what you had=20
submitted.
 Thanks to everyone! Please test this (with multiple source directories) an=
d=20
let me know if you find anything that needs to be looked at. If you pull=20
down the latest code from CVS and do a build, it includes the multiple=20
directories so we can see it work.
 The only regrettable thing that this commit did is commented out our=20
XMLReportTest. I didn't have time to look into what it would take to switch=
=20
it to be operable with the current ReportTask. It looked like it was passin=
g=20
in command line arguments, which has now changed to a command file, and it=
=20
was just too much for right then. If someone want to convert it (and write=
=20
any other unit tests for the multi-filesets), that would be great.=20
 JT

 On 8/2/05, Grzegorz Lukasik <ha...@gm...> wrote:=20
>=20
> Jeremy,
>=20
> I think there are two things from my patch that are easy to reuse in
> yours. The first is CommandLineBuilder - it puts building-parsing long
> command lines in one place. The second is ability of FileStore (yours
> FileFinder) to compute complexity. Basically it removes complexity
> computation from report classes, and computes complexity exactly for
> files the report is generated for, and at most once for each one. Add
> them to your patch if you like. I will add patches later, if you do
> not want to complicate your solution now.
>=20
> Grzegorz
>=20
> On 8/1/05, Jeremy Thomerson <jer...@gm...> wrote:
> > 1. okay, cool
> > 2. agreed - will change
> > 3. oops, you're right, it was for reference, forgot to remove
> > 4. yeah, i'll remove the jar, too (i think that's the only dependency -=
-
> > i'll check
> > 5. i'll look to see where I did it -- not sure, but probably b/c my=20
> default
> > code template adds a default no-op constructor (something we do at work=
,=20
> so
> > the settings / habits carry over)
> > 6. great suggestions - the kind of things I would normally do, not sure=
=20
> why
> > I didn't on this one
> > 7. I'll add an assert so that we don't get any [potential] JUnit
> > warnings.... even though the main point of the test is a no-op, it's=20
> just to
> > call methods
> >
> > I'll look at his patch, too. I did all of this development offline
> > Saturday, so Saturday morning before I left the house, I saved the fr's=
=20
> and
> > bugs from SF to a text file, but forgot to grab the patches to use as
> > reference / starting point. Sorry to those of you who submitted patches
> > that I forgot to grab. I will look at them before committing, though,=
=20
> and
> > merge anything that they include and I forgot.
> >
> > Once I get these things done, I'll commit unless anyone objects before
> > that....
> >
> > Until then,
> > Jeremy
> >
> >
> > On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
> > > I'll number things for reference:
> > >
> > > 1. I just committed the ChangeLog typo fix to get it out of the way,
> > thanks for catching that.
> > >
> > > 2. It might be better if "othersrc" was called "src2," instead. That=
=20
> way
> > it would show up next to "src" in directory listings and people would=
=20
> notice
> > it more. It also allows for us to have "src3" and higher (I doubt=20
> that'll
> > ever happen... but who knows).
> > >
> > > 3. You have a lot of code commented out in reporting.Main... It looks=
=20
> like
> > most of it was replaced with other code, and I guess you were using it=
=20
> for
> > reference, but I would definitely remove it before committing (if peopl=
e
> > want to see an older version of the code then they can check out an old
> > revision from CVS).
> > >
> > > 4. I like that you stopped using gnu.getopt in reporting.Main. Getopt=
=20
> is
> > kind of overkill, I think, and I'd like to remove that jar.
> > >
> > > 5. Is there any reason you're adding empty constructors ocassionally?
> > I've just been implicitly using the default/parent's constructor.
> > >
> > > 6. In FileFinder.findFile you convert forward slashes to=20
> backslashes... It
> > seems like it would make more sense to do that in addSourceFilePath()
> > instead. And also to create a String filePartReplaced or something=20
> before
> > the loop in findFile instead of doing the search/replace for every
> > iteration. And I'd also vote for converting back slashes to forward
> > slashes, but I'm a Linux guy :-)
> > >
> > > 7. Your faux TestCase for SomeOtherClass doesn't have an assert, it=
=20
> seems
> > like JUnit might warn against that?
> > >
> > > You might want to work with Grzegorz Lukasik or see if he does=20
> anything in
> > his patch that you might want to do in yours:
> > >
> >=20
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1245454&grou=
p_id=3D130558&atid=3D720017
> > >
> > > -Mark
> > >
> > >
> > > > -----Original Message-----
> > > > From: cob...@li...
> > > > [mailto: cob...@li...]
> > On
> > > > Behalf Of Jeremy Thomerson
> > > > Sent: Saturday, July 30, 2005 10:26 PM
> > > > To: Mark Doliner
> > > > Cc: cob...@li...
> > > > Subject: [Cobertura-devel] Re: Cobertura 1.5
> > > >
> > > > I spent a few hours today making instrumentation and reporting work
> > > > with multiple source directories. Rather than committing it, I am
> > > > sending out the patch, asking for someone to review it. It also add=
s
> > > > a second directory of source (just one simple faux class) so that w=
e
> > > > have the multiple filesets / multiple source directories in our
> > > > instrumentation and reporting build.
> > > >
> > > > I didn't have time to update any documentation that we have for=20
> usage,
> > > > so if someone could update that (assuming that everyone likes this
> > > > solution), that would be great. Also, I just realized that the
> > > > reporting task should be backwards-compatible with the old srcdir
> > > > attribute, but I don't think I remembered to do that with the
> > > > instrumentation task. If I didn't, but everyone likes this patch,
> > > > I'll commit these changes and add that to the instrumentation class
> > > > for backwards compatibility.
> > > >
> > > > Please let me know what you think.
> > > >
> > > > Jeremy Thomerson
> > > >
> > > > On 7/27/05, M C < mor...@ya...> wrote:
> > > > > Mark Doliner wrote:
> > > > > >Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > > > >It still doesn't supported multiple source
> > > > > directories >for reporting (I REALLY need to look at
> > > > > that patch), >or multiple class directories for
> > > > > instrumenting, but >there are a lot of other changes.
> > > > > >What do you guys think?
> > > > >
> > > > > IMHO Without the patch for multiple source directories
> > > > > I personally do not see the point of a release now.
> > > > > Better to wait for the real thing.
> > > > >
> > > > > Cheers,
> > > > > Morten
> > >
> > >
> > >
> >
> >
>=20
>=20
>

Re: [Cobertura-devel] Re: Cobertura 1.5

[Grzegorz L. <ha...@gm...>]

Jeremy,

I think there are two things from my patch that are easy to reuse in
yours. The first is CommandLineBuilder - it puts building-parsing long
command lines in one place. The second is ability of FileStore (yours
FileFinder) to compute complexity. Basically it removes complexity
computation from report classes, and computes complexity exactly for=20
files the report is generated for, and at most once for each one. Add
them to your patch if you like. I will add patches later, if you do
not want to complicate your solution now.

Grzegorz

On 8/1/05, Jeremy Thomerson <jer...@gm...> wrote:
> 1. okay, cool
>  2. agreed - will change
>  3. oops, you're right, it was for reference, forgot to remove
>  4. yeah, i'll remove the jar, too (i think that's the only dependency --
> i'll check
>  5. i'll look to see where I did it -- not sure, but probably b/c my defa=
ult
> code template adds a default no-op constructor (something we do at work, =
so
> the settings / habits carry over)
>  6. great suggestions - the kind of things I would normally do, not sure =
why
> I didn't on this one
>  7. I'll add an assert so that we don't get any [potential] JUnit
> warnings.... even though the main point of the test is a no-op, it's just=
 to
> call methods
> =20
>  I'll look at his patch, too.  I did all of this development offline
> Saturday, so Saturday morning before I left the house, I saved the fr's a=
nd
> bugs from SF to a text file, but forgot to grab the patches to use as
> reference / starting point.  Sorry to those of you who submitted patches
> that I forgot to grab.  I will look at them before committing, though, an=
d
> merge anything that they include and I forgot.
> =20
>  Once I get these things done, I'll commit unless anyone objects before
> that....
> =20
>  Until then,
>  Jeremy
>=20
>=20
> On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
> > I'll number things for reference:
> >=20
> > 1. I just committed the ChangeLog typo fix to get it out of the way,
> thanks for catching that.
> >=20
> > 2. It might be better if "othersrc" was called "src2," instead.  That w=
ay
> it would show up next to "src" in directory listings and people would not=
ice
> it more.  It also allows for us to have "src3" and higher (I doubt that'l=
l
> ever happen... but who knows).
> >=20
> > 3. You have a lot of code commented out in reporting.Main... It looks l=
ike
> most of it was replaced with other code, and I guess you were using it fo=
r
> reference, but I would definitely remove it before committing (if people
> want to see an older version of the code then they can check out an old
> revision from CVS).
> >=20
> > 4. I like that you stopped using gnu.getopt in reporting.Main.  Getopt =
is
> kind of overkill, I think, and I'd like to remove that jar.
> >=20
> > 5. Is there any reason you're adding empty constructors ocassionally?=
=20
> I've just been implicitly using the default/parent's constructor.
> >=20
> > 6. In FileFinder.findFile you convert forward slashes to backslashes...=
 It
> seems like it would make more sense to do that in addSourceFilePath()
> instead.  And also to create a String filePartReplaced or something befor=
e
> the loop in findFile instead of doing the search/replace for every
> iteration.  And I'd also vote for converting back slashes to forward
> slashes, but I'm a Linux guy :-)
> >=20
> > 7. Your faux TestCase for SomeOtherClass doesn't have an assert, it see=
ms
> like JUnit might warn against that?
> >=20
> > You might want to work with Grzegorz Lukasik or see if he does anything=
 in
> his patch that you might want to do in yours:=20
> >
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1245454&grou=
p_id=3D130558&atid=3D720017
> >=20
> > -Mark
> >=20
> >=20
> > > -----Original Message-----
> > > From: cob...@li...
> > > [mailto: cob...@li...]
> On
> > > Behalf Of Jeremy Thomerson
> > > Sent: Saturday, July 30, 2005 10:26 PM
> > > To: Mark Doliner
> > > Cc: cob...@li...
> > > Subject: [Cobertura-devel] Re: Cobertura 1.5
> > >
> > > I spent a few hours today making instrumentation and reporting work
> > > with multiple source directories.  Rather than committing it, I am=20
> > > sending out the patch, asking for someone to review it.  It also adds
> > > a second directory of source (just one simple faux class) so that we
> > > have the multiple filesets / multiple source directories in our=20
> > > instrumentation and reporting build.
> > >
> > > I didn't have time to update any documentation that we have for usage=
,
> > > so if someone could update that (assuming that everyone likes this
> > > solution), that would be great.  Also, I just realized that the=20
> > > reporting task should be backwards-compatible with the old srcdir
> > > attribute, but I don't think I remembered to do that with the
> > > instrumentation task.  If I didn't, but everyone likes this patch,
> > > I'll commit these changes and add that to the instrumentation class
> > > for backwards compatibility.
> > >
> > > Please let me know what you think.
> > >
> > > Jeremy Thomerson
> > >
> > > On 7/27/05, M C < mor...@ya...> wrote:
> > > > Mark Doliner wrote:
> > > > >Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > > >It still doesn't supported multiple source=20
> > > > directories >for reporting (I REALLY need to look at
> > > > that patch), >or multiple class directories for
> > > > instrumenting, but >there are a lot of other changes.
> > > > >What do you guys think?=20
> > > >
> > > > IMHO Without the patch for multiple source directories
> > > > I personally do not see the point of a release now.
> > > > Better to wait for the real thing.
> > > >
> > > > Cheers,=20
> > > > Morten
> >=20
> >=20
> >=20
>=20
>

Re: [Cobertura-devel] urgent----0% coverage

[Grzegorz L. <ha...@gm...>]

Are you sure the classpath is good? Some files are in ThemePhase-6
subdirectory of workspace, and some are directly under workspace (it
is rather unusual for Eclipse projects). The missing class
net/sourceforge/cobertura/coveragedata/HasBeenInstrumented is
contained inside cobertura.jar distribution (can you verify, that
cobertura.jar contains this file?).

Please feel free to contact me on Yahoo Messenger, my nick is hauserx .

Grzegorz

On 8/2/05, lokesh <lok...@wi...> wrote:
>=20
> Hi Grzegorz,
>=20
> Still having some problem.........help me out...
>=20
>=20
> These are the jars in the classpath:
>=20
>           c:\Eclipse\workspace\cobertura.jar;
>           c:\Eclipse\workspace\build\instrumented;
>           c:\Eclipse\workspace\build\classes;
>           C:\Eclipse\workspace\cobertura.jar;
>           C:\Eclipse\workspace\ThemePhase-6\log4j-1.2.9.jar;
>           C:\Eclipse\workspace\ThemePhase-6\java-getopt-1.0.9.jar;
>           C:\Eclipse\workspace\ThemePhase-6\jakarta-oro-2.0.8.jar;
>           C:\Eclipse\workspace\ThemePhase-6\ccl.jar;
>           C:\Eclipse\workspace\ThemePhase-6\javancss.jar;
>           C:\Eclipse\workspace\ThemePhase-6\java-getopt-1.0.9.jar;
>           C:\Eclipse\workspace\ThemePhase-6\asm-2.0.RC1.jar;
>=20
> I am getting this exception when I try to invoke the instrumented main
> class.
>=20
>=20
> Exception in thread "main" java.lang.NoClassDefFoundError:
> > > net/sourceforge/cobertura/coveragedata/HasBeenInstrumented
> > >         at java.lang.ClassLoader.defineClass1(Native Method)
> > >         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> > >         at
> > >
> > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
> > >         at
> > > java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> > >         at
> > java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> > >         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> > >         at
> > java.security.AccessController.doPrivileged(Native Method)
> > >         at
> > java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> > >         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> > >         at
> > > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
> > >         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> > >         at
> > > java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> -lokesh.
>=20
> -----Original Message-----
> From: Grzegorz Lukasik [mailto:ha...@gm...]
> Sent: Tuesday, August 02, 2005 7:58 PM
> To: lok...@wi...
> Cc: Cobertura-devel
> Subject: Re: [Cobertura-devel] urgent----0% coverage
>=20
> .ser file will be updated after application ends it work - that is
> after java virtual machine shutdown.
>=20
> Be aware, that instrumented classes should be in the classpath
> *before* original classes (if you instrument classes to separate
> directory).
>=20
> Cobertura will update .ser file in the directory that the application
> was started - or if there is no such a file, a new will be created, so
> put .ser file produced after instrumentation in the direcory you run
> the application (you can also use net.sourceforge.cobertura.datafile,
> see here http://cobertura.sourceforge.net/commandlinereference.html
> for an example).
>=20
> Do you still have the problem?
>=20
> Grzegorz
>=20
> On 8/2/05, lokesh <lok...@wi...> wrote:
> >
> >
> >
> > Hi,
> >
> >
> >
> > I'm attempting to use Cobertura for the first time and the report
> shows up
> > as 0% coverage. I don't have unit tests.
> >
> > While running my application I think the .ser file is not getting
> updated,
> > the time stamp remains same.
> >
> >
> >
> > Could any one please tell me how to proceed after instrumenting the
> classes.
> >
> >
> >
> > Thanks,
> >
> > Lokesh.
> >
> >
> >
> >
>=20
>=20
> Confidentiality Notice
> The information contained in this electronic
> message and any attachments to this message are
> intended for the exclusive use of the addressee(s)
> and may contain confidential or privileged information.
> If you are not the intended recipient, please notify
> the sender at Wipro or Mai...@wi... immediately
> and destroy all copies of this message and any attachments.
>

Re: [SPAM-LOW] RE: [Cobertura-devel] Cobertura 1.5

[Jeremy T. <jer...@gm...>]

I made all the changes last night that we mentioned above, but I'm not goin=
g=20
to commit until I have time to integrate pieces of everyone else's patches,=
=20
too (since Grzegorz and James had additional unit tests as well, I'd like t=
o=20
integrate those). I'll do this tonight.

I ended up working much later than I though I would while we were managing =
a=20
release.

Until then...
Jeremy

On 8/1/05, Jeremy Thomerson <jer...@gm...> wrote:
>=20
> I'd rather see us commit / test the multiple fileset fixes and release in=
=20
> a couple of days personally. The multiple fileset thing seems to be the=
=20
> biggest thing that has been asked for by users.=20
>=20
> I agree with the publicity generated by releases, but the more we have,=
=20
> the more people have the potential for thinking that we over-release, so=
=20
> they ignore the new features, especially when they're looking for a featu=
re=20
> (i.e. multiple filesets) and it's not released (i.e. if we release 1.5now=
).
>=20
> Just my $0.02....
>=20
> Just wondering, if I commit the multiple fileset changes tonight.... how=
=20
> many on this list would be willing / able to take the latest build from C=
VS=20
> and test in their setup over the next few days (let's say Tuesday,=20
> Wednesday, Thursday) so that we can be sure it's production-ready, and th=
en=20
> release Friday?
>=20
> If we could have three or more people test it wherever they currently use=
=20
> Cobertura, it would be great. This way we also ensure=20
> backwards-compatibility.
>=20
> Jeremy
>=20
> On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
> >=20
> > > -----Original Message-----
> > > To: cob...@li...
> > > Subject: RE: [Cobertura-devel] Cobertura 1.5
> > >
> > > Mark Doliner wrote:=20
> > > > Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > > It still doesn't supported multiple source
> > > > directories for reporting (I REALLY need to look at
> > > > that patch), or multiple class directories for=20
> > > > instrumenting, but there are a lot of other changes.
> > > > What do you guys think?
> > >
> > > IMHO Without the patch for multiple source directories
> > > I personally do not see the point of a release now.=20
> > > Better to wait for the real thing.
> >=20
> > I've been numbering things like crazy lately:
> >=20
> > 1. Releasing is easy.
> > 2. Releasing gives us publicity (announcement on freshmeat.net=20
> > <http://freshmeat.net>, etc).
> > 3. I'm completely willing to release now and then again a week later.
> > 4. I don't really see a difference between releasing 1.5 now and then=
=20
> > 1.6 next week vs. releasing 1.5beta now and then 1.5final next week.
> > 5. I try to avoid making lots of changes to code and then releasing=20
> > without waiting a few days to let the dust settle. And these changes fo=
r=20
> > multiple source directories seem pretty large, to me
> > 6. There are a lot of changes in 1.5 that I'd like to get out the door.
> >=20
> > -Mark
> >=20
> >=20
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick<http:=
//ads.osdn.com/?ad_idt77&alloc_id%16492&opclick>
> > _______________________________________________
> > Cobertura-devel mailing list
> > Cob...@li...
> > https://lists.sourceforge.net/lists/listinfo/cobertura-devel
> >=20
> >=20
>

RE: [Cobertura-devel] urgent----0% coverage

[Mark D. <Mar...@sa...>]

..build\instrumented\main.

You want your application to use the instrumented classes whenever =
possible.  However, it does not make sense to have an instrumented =
version of some types of class files (RMI stubs, skels, interfaces, =
etc).  For these files the original version should be used.

-Mark

> -----Original Message-----
> From: lokesh [mailto:lok...@wi...]=20
> Sent: Tuesday, August 02, 2005 11:03 AM
> To: Mark Doliner
> Subject: RE: [Cobertura-devel] urgent----0% coverage
>=20
>=20
> Which one I should invoke for running the application:=20
> ..build\instrumented or ..build\classes main.
>=20
> And please explain me the reason
>=20
> -lokesh.
>=20
> -----Original Message-----
> From: Mark Doliner [mailto:Mar...@sa...]=20
> Sent: Tuesday, August 02, 2005 8:24 PM
> To: lok...@wi...
> Cc: cob...@li...
> Subject: RE: [Cobertura-devel] urgent----0% coverage
>=20
> 1. e. When you invoke the main method from the instrumented=20
> classes, are
> you forking or otherwise running the class in a different=20
> JVM?  This JVM
> must terminate before you run cobertura-report
>=20
> 2. You need cobertura.jar in your classpath when running (along with
> log4j.jar)
>=20
> 3. You need the ..\Build\classes folder in your classpath (after
> ..\Build\instrumented, of course).  Cobertura can't instrument
> interfaces and classes that do not contain debug information, and it
> does not currently copy these classes to the instrumented directory
>=20
> -Mark
>=20
> > -----Original Message-----
> > From: lokesh [mailto:lok...@wi...]=20
> > Sent: Tuesday, August 02, 2005 10:47 AM
> > To: Mark Doliner
> > Subject: RE: [Cobertura-devel] urgent----0% coverage
> >=20
> >=20
> > Hi mark,
> >=20
> > I am facing these problems,
> >=20
> > 1. I am doing the following steps for generating the reports:
> > 	a. compile my source code and generate the class files to some
> > ..\Build\classes folder.=20
> > 	b. set all the jars to the classpath(jars related to cobertura).
> > 	c. instrument my class files in the ..Build\classes to
> > ..Build\instrumented folder.
> > 	d. set the instrumented folder path before the uninstrumented
> > folder 	   path to the classpath.
> > 	e. invoke the main method found in the instrumented classes.
> > 	d. generate the report using the same ser file.=20
> >=20
> >=20
> > 2. Exception in thread "main" java.lang.NoClassDefFoundError:
> > net/sourceforge/cobertura/coveragedata/HasBeenInstrumented
> >         at java.lang.ClassLoader.defineClass1(Native Method)
> >         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> >         at
> >=20
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
> >         at=20
> > java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> >         at=20
> java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> >         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> >         at=20
> java.security.AccessController.doPrivileged(Native Method)
> >         at=20
> java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> >         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> >         at=20
> > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
> >         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> >         at=20
> > java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> >=20
> > ---------I have all the jars set in the classpath.
> >=20
> > 3. some classes are missing in the instrumented classes.(so I=20
> > am getting
> > noclassdeffounderror)
> >=20
> > please help me out in these issues.
> >=20
> > Thanks,
> > Lokesh.
> >=20
> >=20
> > -----Original Message-----
> > From: Mark Doliner [mailto:Mar...@sa...]=20
> > Sent: Tuesday, August 02, 2005 7:40 PM
> > To: lok...@wi...
> > Subject: RE: [Cobertura-devel] urgent----0% coverage
> >=20
> > > -----Original Message-----
> > > From: cob...@li...=20
> > > [mailto:cob...@li...] On=20
> > > Behalf Of lokesh
> > > Sent: Tuesday, August 02, 2005 8:13 AM
> > > To: cob...@li...
> > > Subject: [Cobertura-devel] urgent----0% coverage
> > >=20
> > > Hi,
> > > =20
> > > I'm attempting to use Cobertura for the first time and the=20
> > > report shows up as 0% coverage. I don't have unit tests.
> > > While running my application I think the .ser file is not=20
> > > getting updated, the time stamp remains same.
> > > =20
> > > Could any one please tell me how to proceed after=20
> > > instrumenting the classes.
> >=20
> > Two of the more likely things that could be happening are:
> >=20
> > 1. You're not using the instrumented classes when running your
> > application.  The instrumented classes should be in your=20
> > classpath, and
> > they should appear BEFORE the non-instrumented classes.
> >=20
> > 2. You ARE using instrumented classes, but they're creating=20
> > an ser file
> > in a different location than the original one.  The default=20
> > location is
> > the directory from where your application was started
> >=20
> > Hope that helps,
> > Mark
> >=20
> >=20
> >=20
> >=20
> > Confidentiality Notice=20
> >=20
> > The information contained in this electronic message and any=20
> > attachments to this message are intended
> > for the exclusive use of the addressee(s) and may contain=20
> > confidential or privileged information. If
> > you are not the intended recipient, please notify the sender=20
> > at Wipro or Mai...@wi... immediately
> > and destroy all copies of this message and any attachments.
> >=20
>=20
>=20
>=20
>=20
> Confidentiality Notice=20
>=20
> The information contained in this electronic message and any=20
> attachments to this message are intended
> for the exclusive use of the addressee(s) and may contain=20
> confidential or privileged information. If
> you are not the intended recipient, please notify the sender=20
> at Wipro or Mai...@wi... immediately
> and destroy all copies of this message and any attachments.
>=20

RE: [Cobertura-devel] urgent----0% coverage

[Mark D. <Mar...@sa...>]

1. e. When you invoke the main method from the instrumented classes, are =
you forking or otherwise running the class in a different JVM?  This JVM =
must terminate before you run cobertura-report

2. You need cobertura.jar in your classpath when running (along with =
log4j.jar)

3. You need the ..\Build\classes folder in your classpath (after =
..\Build\instrumented, of course).  Cobertura can't instrument =
interfaces and classes that do not contain debug information, and it =
does not currently copy these classes to the instrumented directory

-Mark

> -----Original Message-----
> From: lokesh [mailto:lok...@wi...]=20
> Sent: Tuesday, August 02, 2005 10:47 AM
> To: Mark Doliner
> Subject: RE: [Cobertura-devel] urgent----0% coverage
>=20
>=20
> Hi mark,
>=20
> I am facing these problems,
>=20
> 1. I am doing the following steps for generating the reports:
> 	a. compile my source code and generate the class files to some
> ..\Build\classes folder.=20
> 	b. set all the jars to the classpath(jars related to cobertura).
> 	c. instrument my class files in the ..Build\classes to
> ..Build\instrumented folder.
> 	d. set the instrumented folder path before the uninstrumented
> folder 	   path to the classpath.
> 	e. invoke the main method found in the instrumented classes.
> 	d. generate the report using the same ser file.=20
>=20
>=20
> 2. Exception in thread "main" java.lang.NoClassDefFoundError:
> net/sourceforge/cobertura/coveragedata/HasBeenInstrumented
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>         at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
>         at=20
> java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>         at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>         at=20
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at=20
> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>=20
> ---------I have all the jars set in the classpath.
>=20
> 3. some classes are missing in the instrumented classes.(so I=20
> am getting
> noclassdeffounderror)
>=20
> please help me out in these issues.
>=20
> Thanks,
> Lokesh.
>=20
>=20
> -----Original Message-----
> From: Mark Doliner [mailto:Mar...@sa...]=20
> Sent: Tuesday, August 02, 2005 7:40 PM
> To: lok...@wi...
> Subject: RE: [Cobertura-devel] urgent----0% coverage
>=20
> > -----Original Message-----
> > From: cob...@li...=20
> > [mailto:cob...@li...] On=20
> > Behalf Of lokesh
> > Sent: Tuesday, August 02, 2005 8:13 AM
> > To: cob...@li...
> > Subject: [Cobertura-devel] urgent----0% coverage
> >=20
> > Hi,
> > =20
> > I'm attempting to use Cobertura for the first time and the=20
> > report shows up as 0% coverage. I don't have unit tests.
> > While running my application I think the .ser file is not=20
> > getting updated, the time stamp remains same.
> > =20
> > Could any one please tell me how to proceed after=20
> > instrumenting the classes.
>=20
> Two of the more likely things that could be happening are:
>=20
> 1. You're not using the instrumented classes when running your
> application.  The instrumented classes should be in your=20
> classpath, and
> they should appear BEFORE the non-instrumented classes.
>=20
> 2. You ARE using instrumented classes, but they're creating=20
> an ser file
> in a different location than the original one.  The default=20
> location is
> the directory from where your application was started
>=20
> Hope that helps,
> Mark
>=20
>=20
>=20
>=20
> Confidentiality Notice=20
>=20
> The information contained in this electronic message and any=20
> attachments to this message are intended
> for the exclusive use of the addressee(s) and may contain=20
> confidential or privileged information. If
> you are not the intended recipient, please notify the sender=20
> at Wipro or Mai...@wi... immediately
> and destroy all copies of this message and any attachments.
>=20

Re: [Cobertura-devel] urgent----0% coverage

[Grzegorz L. <ha...@gm...>]

.ser file will be updated after application ends it work - that is
after java virtual machine shutdown.

Be aware, that instrumented classes should be in the classpath
*before* original classes (if you instrument classes to separate
directory).

Cobertura will update .ser file in the directory that the application
was started - or if there is no such a file, a new will be created, so
put .ser file produced after instrumentation in the direcory you run
the application (you can also use net.sourceforge.cobertura.datafile,
see here http://cobertura.sourceforge.net/commandlinereference.html
for an example).

Do you still have the problem?

Grzegorz

On 8/2/05, lokesh <lok...@wi...> wrote:
> =20
> =20
>=20
> Hi,=20
>=20
>  =20
>=20
> I'm attempting to use Cobertura for the first time and the report shows u=
p
> as 0% coverage. I don't have unit tests.=20
>=20
> While running my application I think the .ser file is not getting updated=
,
> the time stamp remains same.=20
>=20
>  =20
>=20
> Could any one please tell me how to proceed after instrumenting the class=
es.
>=20
>  =20
>=20
> Thanks,=20
>=20
> Lokesh.=20
>=20
>  =20
>=20
>

[Cobertura-devel] urgent----0% coverage

[lokesh <lok...@wi...>]

Hi,
 
I'm attempting to use Cobertura for the first time and the report shows
up as 0% coverage. I don't have unit tests.
While running my application I think the .ser file is not getting
updated, the time stamp remains same.
 
Could any one please tell me how to proceed after instrumenting the
classes.
 
Thanks,
Lokesh.
 
 

Re: [SPAM-LOW] RE: [Cobertura-devel] Cobertura 1.5

[Jeremy T. <jer...@gm...>]

I'd rather see us commit / test the multiple fileset fixes and release in a=
=20
couple of days personally. The multiple fileset thing seems to be the=20
biggest thing that has been asked for by users.=20

I agree with the publicity generated by releases, but the more we have, the=
=20
more people have the potential for thinking that we over-release, so they=
=20
ignore the new features, especially when they're looking for a feature (i.e=
.=20
multiple filesets) and it's not released (i.e. if we release 1.5 now).

Just my $0.02....

Just wondering, if I commit the multiple fileset changes tonight.... how=20
many on this list would be willing / able to take the latest build from CVS=
=20
and test in their setup over the next few days (let's say Tuesday,=20
Wednesday, Thursday) so that we can be sure it's production-ready, and then=
=20
release Friday?

If we could have three or more people test it wherever they currently use=
=20
Cobertura, it would be great. This way we also ensure=20
backwards-compatibility.

Jeremy

On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
>=20
> > -----Original Message-----
> > To: cob...@li...
> > Subject: RE: [Cobertura-devel] Cobertura 1.5
> >
> > Mark Doliner wrote:
> > > Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > It still doesn't supported multiple source
> > > directories for reporting (I REALLY need to look at
> > > that patch), or multiple class directories for
> > > instrumenting, but there are a lot of other changes.
> > > What do you guys think?
> >
> > IMHO Without the patch for multiple source directories
> > I personally do not see the point of a release now.
> > Better to wait for the real thing.
>=20
> I've been numbering things like crazy lately:
>=20
> 1. Releasing is easy.
> 2. Releasing gives us publicity (announcement on freshmeat.net<http://fre=
shmeat.net>,=20
> etc).
> 3. I'm completely willing to release now and then again a week later.
> 4. I don't really see a difference between releasing 1.5 now and then 1.6=
next week vs. releasing=20
> 1.5beta now and then 1.5final next week.
> 5. I try to avoid making lots of changes to code and then releasing=20
> without waiting a few days to let the dust settle. And these changes for=
=20
> multiple source directories seem pretty large, to me
> 6. There are a lot of changes in 1.5 that I'd like to get out the door.
>=20
> -Mark
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20
>

Re: [Cobertura-devel] Re: Cobertura 1.5

[Jeremy T. <jer...@gm...>]

1. okay, cool
2. agreed - will change
3. oops, you're right, it was for reference, forgot to remove
4. yeah, i'll remove the jar, too (i think that's the only dependency --=20
i'll check
5. i'll look to see where I did it -- not sure, but probably b/c my default=
=20
code template adds a default no-op constructor (something we do at work, so=
=20
the settings / habits carry over)
6. great suggestions - the kind of things I would normally do, not sure why=
=20
I didn't on this one
7. I'll add an assert so that we don't get any [potential] JUnit=20
warnings.... even though the main point of the test is a no-op, it's just t=
o=20
call methods

I'll look at his patch, too. I did all of this development offline Saturday=
,=20
so Saturday morning before I left the house, I saved the fr's and bugs from=
=20
SF to a text file, but forgot to grab the patches to use as reference /=20
starting point. Sorry to those of you who submitted patches that I forgot t=
o=20
grab. I will look at them before committing, though, and merge anything tha=
t=20
they include and I forgot.

Once I get these things done, I'll commit unless anyone objects before=20
that....

Until then,
Jeremy

On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
>=20
> I'll number things for reference:
>=20
> 1. I just committed the ChangeLog typo fix to get it out of the way,=20
> thanks for catching that.
>=20
> 2. It might be better if "othersrc" was called "src2," instead. That way=
=20
> it would show up next to "src" in directory listings and people would not=
ice=20
> it more. It also allows for us to have "src3" and higher (I doubt that'll=
=20
> ever happen... but who knows).
>=20
> 3. You have a lot of code commented out in reporting.Main... It looks lik=
e=20
> most of it was replaced with other code, and I guess you were using it fo=
r=20
> reference, but I would definitely remove it before committing (if people=
=20
> want to see an older version of the code then they can check out an old=
=20
> revision from CVS).
>=20
> 4. I like that you stopped using gnu.getopt in reporting.Main. Getopt is=
=20
> kind of overkill, I think, and I'd like to remove that jar.
>=20
> 5. Is there any reason you're adding empty constructors ocassionally? I'v=
e=20
> just been implicitly using the default/parent's constructor.
>=20
> 6. In FileFinder.findFile you convert forward slashes to backslashes... I=
t=20
> seems like it would make more sense to do that in addSourceFilePath()=20
> instead. And also to create a String filePartReplaced or something before=
=20
> the loop in findFile instead of doing the search/replace for every=20
> iteration. And I'd also vote for converting back slashes to forward slash=
es,=20
> but I'm a Linux guy :-)
>=20
> 7. Your faux TestCase for SomeOtherClass doesn't have an assert, it seems=
=20
> like JUnit might warn against that?
>=20
> You might want to work with Grzegorz Lukasik or see if he does anything i=
n=20
> his patch that you might want to do in yours:
>=20
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1245454&grou=
p_id=3D130558&atid=3D720017
>=20
> -Mark
>=20
>=20
> > -----Original Message-----
> > From: cob...@li...
> > [mailto:cob...@li...] On
> > Behalf Of Jeremy Thomerson
> > Sent: Saturday, July 30, 2005 10:26 PM
> > To: Mark Doliner
> > Cc: cob...@li...
> > Subject: [Cobertura-devel] Re: Cobertura 1.5
> >
> > I spent a few hours today making instrumentation and reporting work
> > with multiple source directories. Rather than committing it, I am
> > sending out the patch, asking for someone to review it. It also adds
> > a second directory of source (just one simple faux class) so that we
> > have the multiple filesets / multiple source directories in our
> > instrumentation and reporting build.
> >
> > I didn't have time to update any documentation that we have for usage,
> > so if someone could update that (assuming that everyone likes this
> > solution), that would be great. Also, I just realized that the
> > reporting task should be backwards-compatible with the old srcdir
> > attribute, but I don't think I remembered to do that with the
> > instrumentation task. If I didn't, but everyone likes this patch,
> > I'll commit these changes and add that to the instrumentation class
> > for backwards compatibility.
> >
> > Please let me know what you think.
> >
> > Jeremy Thomerson
> >
> > On 7/27/05, M C <mor...@ya...> wrote:
> > > Mark Doliner wrote:
> > > >Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > >It still doesn't supported multiple source
> > > directories >for reporting (I REALLY need to look at
> > > that patch), >or multiple class directories for
> > > instrumenting, but >there are a lot of other changes.
> > > >What do you guys think?
> > >
> > > IMHO Without the patch for multiple source directories
> > > I personally do not see the point of a release now.
> > > Better to wait for the real thing.
> > >
> > > Cheers,
> > > Morten
>=20
>=20
>

RE: [Cobertura-devel] Cobertura 1.5

[Mark D. <Mar...@sa...>]

> -----Original Message-----
> To: cob...@li...
> Subject: RE: [Cobertura-devel] Cobertura 1.5
>=20
> Mark Doliner wrote:
> > Hi, I'm thinking about releasing Cobertura 1.5 soon.=20
> > It still doesn't supported multiple source
> > directories for reporting (I REALLY need to look at
> > that patch), or multiple class directories for
> > instrumenting, but there are a lot of other changes.
> > What do you guys think?
>=20
> IMHO Without the patch for multiple source directories
> I personally do not see the point of a release now.
> Better to wait for the real thing.

I've been numbering things like crazy lately:

1. Releasing is easy.
2. Releasing gives us publicity (announcement on freshmeat.net, etc).
3. I'm completely willing to release now and then again a week later.
4. I don't really see a difference between releasing 1.5 now and then =
1.6 next week vs. releasing 1.5beta now and then 1.5final next week.
5. I try to avoid making lots of changes to code and then releasing =
without waiting a few days to let the dust settle.  And these changes =
for multiple source directories seem pretty large, to me
6. There are a lot of changes in 1.5 that I'd like to get out the door.

-Mark

RE: [Cobertura-devel] Re: Cobertura 1.5

[Mark D. <Mar...@sa...>]

I'll number things for reference:

1. I just committed the ChangeLog typo fix to get it out of the way, =
thanks for catching that.

2. It might be better if "othersrc" was called "src2," instead.  That =
way it would show up next to "src" in directory listings and people =
would notice it more.  It also allows for us to have "src3" and higher =
(I doubt that'll ever happen... but who knows).

3. You have a lot of code commented out in reporting.Main... It looks =
like most of it was replaced with other code, and I guess you were using =
it for reference, but I would definitely remove it before committing (if =
people want to see an older version of the code then they can check out =
an old revision from CVS).

4. I like that you stopped using gnu.getopt in reporting.Main.  Getopt =
is kind of overkill, I think, and I'd like to remove that jar.

5. Is there any reason you're adding empty constructors ocassionally?  =
I've just been implicitly using the default/parent's constructor.

6. In FileFinder.findFile you convert forward slashes to backslashes... =
It seems like it would make more sense to do that in addSourceFilePath() =
instead.  And also to create a String filePartReplaced or something =
before the loop in findFile instead of doing the search/replace for =
every iteration.  And I'd also vote for converting back slashes to =
forward slashes, but I'm a Linux guy :-)

7. Your faux TestCase for SomeOtherClass doesn't have an assert, it =
seems like JUnit might warn against that?

You might want to work with Grzegorz Lukasik or see if he does anything =
in his patch that you might want to do in yours:
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1245454&grou=
p_id=3D130558&atid=3D720017

-Mark


> -----Original Message-----
> From: cob...@li...=20
> [mailto:cob...@li...] On=20
> Behalf Of Jeremy Thomerson
> Sent: Saturday, July 30, 2005 10:26 PM
> To: Mark Doliner
> Cc: cob...@li...
> Subject: [Cobertura-devel] Re: Cobertura 1.5
>=20
> I spent a few hours today making instrumentation and reporting work
> with multiple source directories.  Rather than committing it, I am
> sending out the patch, asking for someone to review it.  It also adds
> a second directory of source (just one simple faux class) so that we
> have the multiple filesets / multiple source directories in our
> instrumentation and reporting build.
>=20
> I didn't have time to update any documentation that we have for usage,
> so if someone could update that (assuming that everyone likes this
> solution), that would be great.  Also, I just realized that the
> reporting task should be backwards-compatible with the old srcdir
> attribute, but I don't think I remembered to do that with the
> instrumentation task.  If I didn't, but everyone likes this patch,
> I'll commit these changes and add that to the instrumentation class
> for backwards compatibility.
>=20
> Please let me know what you think.
>=20
> Jeremy Thomerson
>=20
> On 7/27/05, M C <mor...@ya...> wrote:
> > Mark Doliner wrote:
> > >Hi, I'm thinking about releasing Cobertura 1.5 soon.=20
> > >It still doesn't supported multiple source
> > directories >for reporting (I REALLY need to look at
> > that patch), >or multiple class directories for
> > instrumenting, but >there are a lot of other changes.
> > >What do you guys think?
> >=20
> > IMHO Without the patch for multiple source directories
> > I personally do not see the point of a release now.
> > Better to wait for the real thing.
> >=20
> > Cheers,
> > Morten

[Cobertura-devel] Re: Cobertura 1.5

[Jeremy T. <jer...@gm...>]

I spent a few hours today making instrumentation and reporting work
with multiple source directories.  Rather than committing it, I am
sending out the patch, asking for someone to review it.  It also adds
a second directory of source (just one simple faux class) so that we
have the multiple filesets / multiple source directories in our
instrumentation and reporting build.

I didn't have time to update any documentation that we have for usage,
so if someone could update that (assuming that everyone likes this
solution), that would be great.  Also, I just realized that the
reporting task should be backwards-compatible with the old srcdir
attribute, but I don't think I remembered to do that with the
instrumentation task.  If I didn't, but everyone likes this patch,
I'll commit these changes and add that to the instrumentation class
for backwards compatibility.

Please let me know what you think.

Jeremy Thomerson

On 7/27/05, M C <mor...@ya...> wrote:
> Mark Doliner wrote:
> >Hi, I'm thinking about releasing Cobertura 1.5 soon.=20
> >It still doesn't supported multiple source
> directories >for reporting (I REALLY need to look at
> that patch), >or multiple class directories for
> instrumenting, but >there are a lot of other changes.
> >What do you guys think?
>=20
> IMHO Without the patch for multiple source directories
> I personally do not see the point of a release now.
> Better to wait for the real thing.
>=20
> Cheers,
> Morten
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September
> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20
>

RE: [Cobertura-devel] Cobertura 1.5

[M C <mor...@ya...>]

Mark Doliner wrote:
>Hi, I'm thinking about releasing Cobertura 1.5 soon. 
>It still doesn't supported multiple source
directories >for reporting (I REALLY need to look at
that patch), >or multiple class directories for
instrumenting, but >there are a lot of other changes.
>What do you guys think?

IMHO Without the patch for multiple source directories
I personally do not see the point of a release now.
Better to wait for the real thing.

Cheers,
Morten

[Cobertura-devel] Todos os Sites de Buscas

[Cadastre-se <cad...@ya...>]

<!-- saved from url=(0022)http://internet.e-mail -->
<html>
<head>
<title>Cadastramento</title>
<meta http-equiv="Content-Type" content="text/html;">
<!--Fireworks MX 2004 Dreamweaver MX 2004 target.  Created Fri Mar 11 15:46:01 GMT-0300 (Hora oficial do Brasil) 2005-->
</head>
<body bgcolor="#ffffff">
<p align="center"><a href="http://www.submitsearch.com.br/cadastramentosite4.htm" target="_blank">Caso 
  n&atilde;o consiga visualizar, clique aqui</a></p>
<table width="650" border="0" align="center" cellpadding="0" cellspacing="0">
<!-- fwtable fwsrc="cadastramento_faixas.png" fwbase="cadastramento_faixas.jpg" fwstyle="Dreamweaver" fwdocid = "1604695900" fwnested="0" -->
  <tr>
   <td><img src="spacer.gif" width="408" height="1" border="0" alt=""></td>
   <td><img src="spacer.gif" width="59" height="1" border="0" alt=""></td>
   <td><img src="spacer.gif" width="183" height="1" border="0" alt=""></td>
   <td><img src="spacer.gif" width="1" height="1" border="0" alt=""></td>
  </tr>

  <tr>
    <td colspan="3"><a href="http://www.submitsearch.com.br/cadastramentosite4.htm" target="_blank"><img name="cadastramento_faixas_r1_c1" src="http://www.submitsearch.com.br/cadastramento_faixas_r1_c1.jpg" width="650" height="137" border="0" alt=""></a></td>
   <td><img src="spacer.gif" width="1" height="137" border="0" alt=""></td>
  </tr>
  <tr>
    <td colspan="3"><a href="http://www.submitsearch.com.br/cadastramentosite4.htm" target="_blank"><img name="cadastramento_faixas_r2_c1" src="http://www.submitsearch.com.br/cadastramento_faixas_r2_c1.jpg" width="650" height="142" border="0" alt=""></a></td>
   <td><img src="spacer.gif" width="1" height="142" border="0" alt=""></td>
  </tr>
  <tr>
    <td rowspan="2"><img name="cadastramento_faixas_r3_c1" src="http://www.submitsearch.com.br/cadastramento_faixas_r3_c1.jpg" width="408" height="41" border="0" alt=""></td>
    <td><a href="http://www.submitsearch.com.br/remover_destinatarios.htm" target="_blank"><img name="cadastramento_faixas_r3_c2" src="http://www.submitsearch.com.br/cadastramento_faixas_r3_c2.jpg" width="59" height="15" border="0" alt=""></a></td>
    <td rowspan="2"><img name="cadastramento_faixas_r3_c3" src="http://www.submitsearch.com.br/cadastramento_faixas_r3_c3.jpg" width="183" height="41" border="0" alt=""></td>
   <td><img src="spacer.gif" width="1" height="15" border="0" alt=""></td>
  </tr>
  <tr>
    <td><img name="cadastramento_faixas_r4_c2" src="http://www.submitsearch.com.br/cadastramento_faixas_r4_c2.jpg" width="59" height="26" border="0" alt=""></td>
   <td><img src="spacer.gif" width="1" height="26" border="0" alt=""></td>
  </tr>
</table>
</body>
</html>

Re: [Cobertura-devel] Cobertura 1.5

[Grzegorz L. <ha...@gm...>]

I think it would be better if 1.5 was released one week later, but
with multiple directories support. Otherwise multiple class support,
that seems to be very helpful for many people, will wait till 1.6 - so
it will be next month or so.

My proposition is to release now a beta version, and release 1.5 with
multiple directories support. Patches are ready - and even if they are
not mature enough, I do not think it will take more than week to have
them implemented right. Also, before 1.5 do not any new functionality,
just fix bugs if needed.

just my 0.02PLN

On 7/26/05, Mark Doliner <Mar...@sa...> wrote:
> Hi, I'm thinking about releasing Cobertura 1.5 soon.  It still doesn't su=
pported multiple source directories for reporting (I REALLY need to look at=
 that patch), or multiple class directories for instrumenting, but there ar=
e a lot of other changes.
>=20
> What do you guys think?  Maybe wait a week and make sure everything is st=
able and release next Tuesday?
> -Mark
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>

[Cobertura-devel] Cobertura 1.5

[Mark D. <Mar...@sa...>]

Hi, I'm thinking about releasing Cobertura 1.5 soon.  It still doesn't =
supported multiple source directories for reporting (I REALLY need to =
look at that patch), or multiple class directories for instrumenting, =
but there are a lot of other changes.

What do you guys think?  Maybe wait a week and make sure everything is =
stable and release next Tuesday?
-Mark