cool thanks we will look at it. Andre started to redo it (i think). Stef
On Sep 2, 2011, at 10:59 AM, Lukas Renggli wrote: >> For the RBRule what would be great (and this was on my overly long todo) was >> a improve the description. >> May be we should have a short and long one. Because something I do not >> understand (well I do most of the times) but >> I would love to get a nice description because we really want to push the >> rules usage. > > Longer descriptions for most rules can be found here: > http://www.refactory.com/RefactoringBrowser/BrowserPagesLintChecks.html > > The #rational should remain a one sentence description for the UI. > >> - get rules automatically run with jenkins > > I've implemented that a long time ago with the rest of the build > system. For example, on the Seaside build > (http://jenkins.lukas-renggli.ch/job/Seaside%203.0/) there is a graph > that shows the change in code critics issues over time ("Checkstyle > Trend"). If you click on the graph or on "Checkstyle Warnings" > (http://jenkins.lukas-renggli.ch/job/Seaside%203.0/715/checkstyleResult/?) > you get detailed reports about all issues and how they change between > the builds. > > The only thing to do is to tell Jenkins to run the report. The syntax > is exactly the same as with running tests, except that you use > HDLintReport instead of HDTestReport. It is all described in the > README text of the Jenkins scripts. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >
