Re: [Ginp-developers] Project Quality

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

Doug Culnane wrote:
> I have a look at Jalopy and the maven plugin and it has got a bit more
> complicated than it used to be.  Basically I have lost patience with
> it.  I can not find a SUN standard configuration so the best match is
> the Maven coding conventions and the Jalopy standard.  It used to be a
> bit easier to use but now it has gone all wizard, gui, product,
> commercial etc... and I therefore it is beyond me to be able to
> integrate it into the project as i used to do.
> 
> I can switch to the SUN standard for checkstyle but this complains a lot
> about the use of {()} etc....
> 
> Therefore I would suggest that we leave it as it is and new code is
> formated manually.  Thank Jalopy for doing 95% of the formating for us
> and the rest we do by hand as and when we can be bothered.  The
> Checkstyle Maven standard is the authority on what is and is not well
> formatted.  Maven issue a formatter config for different IDEs
> (http://maven.apache.org/guides/development/guide-m2-development.html#Maven%20Code%20Style). 
> 
> 
> Is this acceptable to you, or do you have a better idea.?

Yes, that's fine.

We'll take the Jalopy formatting as our "new" starting point. Any work I 
do on the code cleanup will be acceptable as long as it reduces the 
number of maven complaints.

Thanks for taking a sensible decision. We don't want to make work for 
ourselves!

Brian