Re: [Ginp-developers] Project Quality

[Brian B. <br...@Pi...>]

Doug Culnane wrote:
> Dear Brian,
> 
> After your points about code style I thought I would check in a bit of
> Maven QA reporting.  This produces reports that are not good for my ego
> but they are a great way to measure code quality and the quality
> improvements if any...
> 
> Update with
>> svn up
> 
> Generate site locally using:
>> mvn site
> 
> Check out reports at: ginp/target/site/project-reports.html

It worked very well, although I had to run it from a command line.

This was because my Netbeans maven2 had problems finding some 
dependencies when running the custom goal called "site". I'll worry 
about it another time...

> Let me know if we really want this in the live site....?  I am happy to
> publish and I think it will motivate me to improve quality.

No, I don't think this needs to be on the main site until you feel we 
are ready to publish an 0.30 war for download. At that time, I don't see 
a problem confessing to bad style. As you say, with the reports as a 
reminder, it encourages us to do a bit extra whenever working on a 
particular module. No need for explicit objectives, just good intentions.

Of course, now that I can run the reports locally, I'll be able to do 
something myself.

> Also let me know if you want the code formated automatically with Jalopy?

I didn't know about Jalopy, but have just looked at the site at SourceForge.

Q: would you add it to the maven pom.xml so it is run at every build, or 
just a one-time process?

Q: what style would you impose on the project? (I tend to use the Rogue 
Wave Java Style book as my base reference, then modify my code style 
where necessary to fit that of the project I'm working on.)

Brian