> ps: I recommend choosing some coding guidelines for Maven ASAP so that we
> can safely refactor/clean up everything with a single coding style. Due to
> legacy code there are 3 coding styles in it. I would rather prefer we choose
> the Jakarta one (ie Sun) and that we stick to it otherwise it is painful to
> reconfigure an editor to enforce a particular convention each time we move
> from a project to another. (Sorry Jason, I know you use the Allman style in
> Turbine, but you're free to decide whether we should use this one or not for
> Maven. Just shout out loud ;-).
+1 for standardizing on the style used by all other projects in turbine,
rather than the evil whitespace reducing unreadable sun style. =]
it is jakarta-turbine-maven after all right?
^^^^^^^
-- jt
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
