Done. The Coverity web-ui makes this simple for admins to do. Reference for other Coverity admins: On the "Analysis settings" tab, add a "component" whose path is a regexp and you check the "ignore in analysis" box. The list is ordered; drag the new item into the appropriate place and then save. It sometimes take a few moments for the change to be reflected; it reclassifies all the currently known defects based on the regexps of the configured components.
Chris. From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) [mailto:mgrad...@cisco.com] Sent: Tuesday, January 10, 2017 11:33 AM To: vpp-dev@lists.fd.io; hc2...@lists.fd.io Cc: Damjan Marion (damarion) <damar...@cisco.com>; Luke, Chris <chris_l...@cable.comcast.com>; Dave Barach (dbarach) <dbar...@cisco.com> Subject: Coverity warnings in generated java files Hi, do you know is there a way to exclude java file / code line from coverity analysis, by adding some code annotation? In case it is not possible (or as a temporary workaround), here is a list of directories, that need exclusion: ./build-vpp-native/vpp/vpp-api/java/jvpp-acl/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-core/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-ioamexport/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-snat/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-ioamtrace/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-ioampot/target/ So we need rule of this kind: ./build-vpp-native/vpp/vpp-api/java/*/target/ Regards, Marek
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
