maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Walding <>
Subject Re: OT: codebase design guidelines - Happy Holidays!
Date Tue, 24 Dec 2002 00:13:41 GMT
I don't believe this is off topic :)  (and if it is, just say "But it's 

Maven Layout:
You'll want to have a look at :

Which shows the current practice for laying out Maven so that you don't 
have to redefine a whole lot of properties.

I tend to make blanket statements like

      Unit Testing

All new code that could possibly fail must have unit-tests. Admittedly 
the coverage isn't 100% yet, but with each release, the Quilt / Clover 
coverage results must not decrease.

      Coverage Testing

The minimum coverage (generate using |maven clean clover:html-report|) 
for any non-trivial class within DataForge is 80%. A trivial class is 
something which has no methods that would reasonably fail; eg. a bean 
with no behaviour except getters and setters. Ideally the level would be 
100%, but given that there are only so many monkey hours in a day, 80% 
is the easy part.

John Casey wrote:

>I just thought I'd toss something out for a little light reading this
>holiday season.  I'm trying to compile all that I've learned over the
>past few years on the nitty-gritty side of project management - codebase
>management.  What I'm trying to nail down is the "correct" way to design
>a project so that it is manageable, usable to new developers, plugs into
>continuous integration tools, etc...
>Anyway, if you have time, I'd love any feedback I can get.
>I already know that I've forgotten to include a section on testing...I'm
>working on that.
>To unsubscribe, e-mail:   <>
>For additional commands, e-mail: <>

View raw message