Re: Code Conventions

Hi Michael,

Michael Homeijer wrote:
> How about using jalopy or another code formatter?
> Is able to add and replace copyright or license headers,
> format code to your conventions, add javadoc header templates and
> remove tabs from your code, organize imports etc.
> 
> With jalopy you have an XML file with settings that contain your code
> standards. Additionally we use checkstyle that checks your code style.
> These are very helpfull tools to support your commandments.

That sounds interesting, in particular for inserting license
headers to all existing files. Any volunteers? :)

When all deadlines are over (this weekend or next week),
we could re-format all existing Java code. In my eyes, this is
the first step towards refactoring and doesn't do any hurt.
But we should beware of re-formatting any XML at all, that
can change semantics!

Andreas


> -----Original Message-----
> From: Andreas Hartmann
> To: [email protected]
> Sent: 5-2-2003 10:05 
> Subject: [Wyonacms-dev] Code Conventions
> 
> 
> And the Wyona team returned from the mountain Zurichberg
> and spake all these words, saying,
> 
> I.  Thou shalt only produce code conforming to the Java
>      code conventions, as they are set down on the page
>      http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html.
> 
> II. Thou shalt not produce any code containing tab-stops.
> 
> 
> And all the people answered together, “We are willing to
> do all the words that the Wyona team has said.â€
> 
> (more commandments - e.g., regarding XML - to follow soon)
> 
> 
> Andreas
> 
> 
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
> 
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev