From cfd93d768e79a349f1e762b92773190295c36980 Mon Sep 17 00:00:00 2001 From: Michał Górny Date: Sun, 24 Jan 2016 23:32:36 +0100 Subject: Replace all herds with appropriate projects (GLEP 67) Replace all uses of herd with appropriate project maintainers, or no maintainers in case of herds requested to be disbanded. --- dev-util/findbugs/metadata.xml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'dev-util/findbugs/metadata.xml') diff --git a/dev-util/findbugs/metadata.xml b/dev-util/findbugs/metadata.xml index 66ae673b690e..549e98606b54 100644 --- a/dev-util/findbugs/metadata.xml +++ b/dev-util/findbugs/metadata.xml @@ -1,7 +1,10 @@ - java + + java@gentoo.org + Java + FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. Static analysis means that FindBugs can find bugs by simply inspecting a program's code: executing the program is not necessary. This makes FindBugs very easy to use: in general, you should be able to use it to look for bugs in your code within a few minutes of downloading it. FindBugs works by analyzing Java bytecode (compiled class files), so you don't even need the program's source code to use it. Because its analysis is sometimes imprecise, FindBugs can report false warnings, which are warnings that do not indicate real errors. In practice, the rate of false warnings reported by FindBugs is less than 50%. findbugs -- cgit v1.2.3-65-gdbad