Can't say anything on the other items, but: On Wed, Dec 5, 2012 at 12:06 AM, Simone Tripodi <[email protected]> wrote: > * code conventions: while everybody agrees that the ALv2.0 header is > mandatory, I'm for giving freedom to each component to chose the > preferred source code convention, the most important thing IMHO is > that when choosing a convention it is respected. This is something to > setup at parent level, since at 99soft we were Maven's conventions > fans and we just set that one :P
I am in favor to have one code convention for all components. It really annoys me all the time at Commons: every each component does have different rules of writing code. Once I get used to a style, I need to adapt another. Although I am not a fan of the Maven conventions, I still would like to suggest the following we ask initial developers on this list if they are fine with the Mvn conventions. If yes, please make it sticky for the whole project. Commons feels much like a mess to me. Once done i also suggest we include a checkstyle test. It should not break the build, if that is possible. If that is not possible we could distribute the checkstyle rules for our IDEs in the /svn/onami/committers folder That all said, I am ready for adapting the Maven style and prefer it before long redundant discussion on code formatting of various components Cheers Christian
