From: "Rainer Klute" <[EMAIL PROTECTED]>
"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
Good idea, I like it.
It gives anybody looking at the code a warning, I like it.
>>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.
Hmmm... what about a timeframe that is shorter the higher the errors are?
For example, if the errors are 20, it could give the user 1 month, if they
are 200, 3 days.
(maybe you can come up with a better function())
>>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.
Correct. As for now, do
build metrics
and the result is in the build/docs/metrics/checkstyle dir.
>>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!
For a start 3 weeks from now.
After that, we can have a function as said above.
>If we can do as outlined above, I vote +1.
Good :-)
Any idea on the correlation function to use between number of errors and
time given?
BTW, I think that your idea of using special javadoc tags to make automatic
information is really cool.
We could use it to generate all sorts of automatic warnings or suggestions.
:-D
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
