Hi guys. Maybe someone can help me before I waste a lot of time. It looks like on August 29 something changed in Code Critics API and after that the command line tool is not capturing all reports.
Cheers. Uko Begin forwarded message: > From: Clément Bera <bera.clem...@gmail.com> > Subject: Re: CodeCritics command line > Date: 31 Mar 2014 19:28:54 GMT+2 > To: Yuriy Tymchuk <yuriy.tymc...@me.com> > Cc: Clément Béra <bera.clem...@gmail.com> > > Hello Yuriy. > > One possibility is that you run it only on a limited number of packages, > here's the APIs to select the packages. > > ./pharo Pharo.image analyse >> maintenancePharo.xml > ./pharo Pharo.image analyse --packages='Kernel*' >> maintenanceKernel.xml > > Alternatively if you look at the plots at build #370 all the curves goes > down. So it may be there were some API changes in code critics there that > broke the tool. I have not looked into it for a long time. > > Cheers > > > 2014-03-31 7:17 GMT-07:00 Yuriy Tymchuk <yuriy.tymc...@me.com>: > Hi Clement, > > Can you help me a bit more. Something is not working for me. When I use the > code critics browser, and run it on the whole system I get (for example) > RBVariableReferencedOnceRule 90 violations, while command line tool gives me > only 3. And this happens with all of the rules (command line tool always > reports very few). Maybe you have a clue what can be a problem, because I’ve > spent a day already without any success. > > Cheers. > Uko >
