What is correct Maven scope of findbugs annotations?

Question

I want to use a library that has the following dependency:

<dependency>   <groupId>com.google.code.findbugs</groupId>   <artifactId>annotations</artifactId>   <version>2.0.3</version> </dependency> 

I read that FindBugs is for static analysis of Java code, so I though it isn't necessary to include in application. Is it safe to exclude the jar with <scope>provided</scope> or with an <exclusion>...</exclusion>?

One reason to exclude it is that there is a company policy against (L)GPL licence.

Answer 1

Yes, you can safely exclude this library. It contains only annotations which do not need to be present at runtime. Take care to have them available for the FindBugs analysis, though.

Note that you should also list jsr305.jar, like this:

<dependency>     <groupId>com.google.code.findbugs</groupId>     <artifactId>annotations</artifactId>     <version>3.0.2</version>     <scope>provided</scope> </dependency> <dependency>     <groupId>com.google.code.findbugs</groupId>     <artifactId>jsr305</artifactId>     <version>3.0.2</version>     <scope>provided</scope> </dependency> 

Both JARs are required to make these annotations work.

Check the most recent findbugs version in Maven Central.

FindBugs is provided under the LGPL, so there should not be any problems for your company. Also, you are merely using FindBugs; you are not developing something derived from FindBugs.

Answer 2

In theory, it should be entirely safe (as defined in the OP's clarifying comment) to exclude the Findbugs transitive dependency. If used correctly, Findbugs should only be used when building the library, not using it. It's likely that someone forgot to add <scope>test</scope> to the Findbugs dependency.

So - go ahead and try the exclusion. Run the application. Do you get classpath errors, application functionality related to the library that doesn't work, or see messages in the logs that seem to be due to not having Findbugs available? If the answer is yes I personally would rethink using this particular library in my application, and would try to find an alternative.

Also, congratulations on doing the classpath check up front! As a general practice, it is a great idea to do what you have done every time you include a library in your application: add the library, then check what other transitive dependencies it brings, and do any necessary classpath clean-up at the start. When I do this I find it makes my debugging sessions much shorter.