Removing "rule generic-catchall-00800"

[Maarc]

It is generating only false positives and its content is already fully covered by our very nicht EJB/JPA/Server resources reports.

[jsight]

@mareknovotny - Can you take a look at this one?

[mareknovotny]

@jsight sure.

[Maarc]

@mareknovotny

As described in the pull request, this rule is generating an important amount of false positives.

Considered that we already have dedicated EJB / JPA ... reports describing what the application is doing, there is no point at keeping this rule. We do not need it any more. It is only generating "noise".

[mareknovotny]

@Maarc I got your point and on that problem I noticed that my original change is missing the important thing to add hints/classifications only if there is not already hint added - this should be in all catchall rules to show up only if there is not any specifics about the matched group.

This change should resolve your concerns with false positive, please try it from #87.

[Maarc]

Hi Marek,

#87 does not solve my "problem". I just want to remove this one rule because it is already covers by other reports (dedicated EJB / JPA reports) and only produces noise.

I still think, that we should comment out this rule.

best regards,

Marc

[jsight]

@rdruss - I agree with @Maarc. What do you think? And is there anything we need to do to document or get approval for this change?

[mareknovotny]

@Maarc @jsight @rdruss I did that in mareknovotny@cb3ea8c

[jsight]

@mareknovotny incorporated this into #87 and I have merged that one.