Giacomo Pati wrote:
>
> Dear all
>
> I've a initial version of the ExcaliburTestCase ready for committment. As it
> comes to packaging some thought need to be made.
>
> >From the Excalibur point of view this class should make it into the distributed
> jar because it eases development based on Excalibur. From a projects point of
> view it is noting that should be deployed into a production environment. The
> possibilities are:
>
> 1. Pack it into avalon-excalibur.jar. As it is only one class a separate
> jar doesn't make much sense.
>
> 2. Make a separate jar (avalon-excalibur-test.jar?). Though it is a single
> class but based on junit it might be justifiable to do so.
>
> You thoughts?
For the time being, I would place it in Excalibur's jar. In the future, I want
to repurpose the Jakarta Avalon Testlet project to be the place for such things.
The new version of the Testlet package would include classes like this one, metrics
gathering classes (I have a C based SLOC counter that measures physical SLOC, logical
SLOC, and number of instances a keyword is used). BTW, the acronym SLOC means
Source Lines Of Code. I also want to put together a Complexity rating engine.
Complexity is computed on a per method basis, and basically you start with 1, and
for each loop (for/do/while), condition (if/else/switch/case), or exception
handling (try/catch/finally) block you add one. That means that you add 1 for
each time you encounter the those keywords really. High complexity ratings
are used to identify which methods or functions are ripe for refactoring. Decent
complexity levels are around 7 and below.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
