RE: [Cobertura-devel] cobertura-runtime.jar?

[Sinke, M. \(GE Healthcare\) <mar...@me...>]

Hi Mark,

I'd be all for splitting the libs. In fact I think we're using too many
libraries now, just because we don't know what the library is.

I like the version number suffix. In fact, we renamed cobertura.jar
version 1.3 to cobertura-1.3.jar (that's a consistent naming policy we
have anyway).

As to logging: let's just use jakarta commons logging. That way we don't
need log4j and commons logging is really tiny. It will fall back to JDK
1.4+ logging if log4j is not available.

Mark.
  _____ =20

"From there to here,
from here to there,
funny things are everywhere."
        - One Fish, Two Fish, Red Fish, Blue Fish, Dr. Seuss
  _____ =20

Mark J. Sinke
Senior Software Architect/Patient Directory Team Lead
GE Healthcare Information Technologies
Clinical Information Technologies Core Infrastructure Platforms=20

T +31 30 692 6000
F +31 30 692 6010
D *381 6446
E mar...@me... <mailto:mar...@me...> =20

www.gehealthcare.com <http://www.gehealthcare.com>=20


-----Original Message-----
From: cob...@li...
[mailto:cob...@li...] On Behalf Of Mark
Doliner
Sent: Friday, June 17, 2005 02:03
To: cob...@li...
Subject: [Cobertura-devel] cobertura-runtime.jar?

Cobertura currently consists of one jar file, and this jar must be on
your classpath when instrumenting, running tests, and reporting.
However, when you actually run your tests, only one of the packages in
this jar is used, and the package only requires log4j.

How do people feel about creating a cobertura.jar and a
cobertura-runtime.jar, where cobertura-runtime.jar contains all the
classes in the package net.sourceforge.cobertura.coveragedata.  And
cobertura.jar would contain everything else (ant tasks, instrumenting
code, reporting code, etc.)

The goal is to make it more clear that asm, ncss, jakarta-oro, etc. are
not required when running instrumenting code.  I think this would help
avoid classpath conflicts with ASM.

Good idea?  Bad idea?  Suggestions for better names for the jars?
Should the jars include the version number in their name
("cobertura-1.5.jar")?  Should the runtime jar still use log4j, or
should we get rid of that dependency?

FYI, I'll be out of town from now until Sunday night.

-Mark


-------------------------------------------------------
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&op=3Dick
_______________________________________________
Cobertura-devel mailing list
Cob...@li...
https://lists.sourceforge.net/lists/listinfo/cobertura-devel