Re: [Ginp-developers] Project Quality

[Doug C. <do...@cu...>]

Brian Burch wrote:
> Q: would you add it to the maven pom.xml so it is run at every build, or 
> just a one-time process?
>   
Yes it goes in the "<build>" section of the POM.  I would bind this in
so it runs on every install phase.
> 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.)
>   
Not sure.  Jalopy is very configurable but it "ships with sensible
default settings (mimicking the Sun Java coding convention)."  I would
use these. 

I could set up Jalopy and you can try it with the command. 
> mvn install

This will format all code.  I will check in Jalopy in the POM and all
the formatted code.  This will be a big change in the subversion
repository, so please tell me when you have everything checked in and
then I will do this.  After that if "mvn install" is run regularly then
the formatting will be stable and only new stuff will get altered. 
However you need to be aware that you and your formatter are changing
code and this can get confusing and create SVN conflicts.

The problem with setting up an IDE is that a project uses multiple
IDEs.  JUnit, Eclipse and Netbeans have now all be used for the GINP. 
Getting these set up the same is not easy.

An alternative is to run Jalopy once from the command line, but this
need to be done regularly.

Another alternative is not to do any formatting but this also has problems.

Let me know what you want?

All the best,

Doug