"Nicola Ken Barozzi" <[EMAIL PROTECTED]> wrote:
>The problem is, where do we store this history?
In a special Javadoc tag for each method or class. Example:
@checkstyle-results: The following is not okay with respect to
coding standards bla bla bla...
@checkstyle-resolve-until: 2002-06-13
>I think it's a big hassle, and 1 month is too much for OS software.
One month was just an example. However, since this is only style
a rather long period is okay. If this annoys someone else than
the author he can go a fix it himself.
>If someone is committing new stuff, he should do so only if checkstyle
>passes with the threshold, ar he knows that it will be reformatted.
Yes. But he must have the tools to check the style himself
before checking his stuff in.
>The problem arises with legacy code, that we have in CVS now.
>
>I think that we can give all devs 3 weeks to clean the code starting from
>now, then the system will kick in.
>
>Is this better?
3 weeks should be okay. But not 3 days or 3 hours or so!
If we can do as outlined above, I vote +1.
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH i. Gr.
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
K�rner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
