Hi Yeah this tools seems at first sight much improved over other tools we have seen in the past, that gives a lot of false positives and noises.
On Wed, Dec 18, 2019 at 8:55 AM Guillaume Nodet <gno...@apache.org> wrote: > > Agreed, we can easily create a profile for that. > In addition, we should quickly review them because some of the alerts are > actual bugs, like the second one at least. > We can filter the ones that coud be investigated: > > https://lgtm.com/projects/g/apache/camel/alerts/?sort=name&dir=ASC&mode=list&tag=correctness%2Clogic%2Creliability > > Le mer. 18 déc. 2019 à 07:58, Jean-Baptiste Onofré <j...@nanthrax.net> a > écrit : > > > Hi Omar, > > > > if it's in a profile, why not, but I don't like such tool "forced" in > > the default build. > > > > Regards > > JB > > > > On 17/12/2019 16:17, Omar Al-Safi wrote: > > > Hello folks, > > > > > > Recently, I stumbled across this code analysis tool https://lgtm.com/ > > and > > > is free for open source integration. It looks pretty good based on the > > > analysis results it gave for camel ( > > > https://lgtm.com/projects/g/apache/camel/) (sure some of them it can be > > > neglected). However, I was wondering, does it make sense to enable it on > > > PRs? For me personally, it could help to some extent to catch potential > > > bugs that hard to spot by the human eye. > > > > > > Regards, > > > Omar > > > > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > > > > -- > ------------------------ > Guillaume Nodet -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
