The documentation site, https://spotbugs.readthedocs.io/, is throwing a NET::ERR_CERT_AUTHORITY_INVALID error:

Cert Details
Subject: ssl403572.cloudflaressl.com
Issuer: COMODO ECC Domain Validation Secure Server CA 2
Expires on: Nov 26, 2020
Current date: Jul 10, 2020

This could be an issue with readthedocs.io or cloudflare, because three out of the six featured projects on the readthedocs.io homepage had the same error, surprisingly with the same certificate.

Chrome will not let you proceed with this cert error, but Edge will.

Hopefully this is something you can fix on your end.

I wonder if we can somehow automate the spotbugs build on github so after merging a PR it could upload generated "daily" build (and Eclipse update site) to the server?

When I am using gradle, the homepage does not provide a hint to start the tool. There is no task spotBugs. When including the gradle pulgin, there is findBugsMain (which currently does not work - see spotbugs/spotbugs#250).

• Could you add somewhere that one has to execute findBugsMain?
• Could you add an example output?
• Could you add information how to apply the plugin fb-contrib. fb is not the same as spotbugs and so I wonder how they are compatible and how I can use these rules within a gradle setting.

The homepage reads

SpotBugs is the spiritual successor of FindBugs

The repository description reads

SpotBugs is FindBugs' successor

I interpret that as complete rewrite of FindBugs. I really wonder, why the code still has some pieces with "findbugs" in it (see e.g. https://github.com/spotbugs/spotbugs/blob/master/gradlePlugin/src/main/java/com/github/spotbugs/SpotBugsPlugin.java). The gradle tasks still seems to be findbugsMain (see spotbugs/spotbugs#250). Why is not everything renamed? It would be really great if that was explained on the homepage.

Is SpotBugs a simple wrapper around findbugs? The exception trace is an indication for that:

  At edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:218)
  At com.github.spotbugs.internal.spotbugs.FindBugsExecuter.runFindbugs(FindBugsExecuter.java:23)

I'm sure that SpotBugs is more. That should be clarified (if possible).

#6 will introduce Git sub-module to store built files to gh-pages branch. After we introduce #6, we need to configure this project to use gh-pages branch to host web site.

Hi,

Environment
Spring Tool Suite

Version: 3.9.1.RELEASE
Build Id: 201710111105
Platform: Eclipse Oxygen.1a (4.7.1a)

I tried to use spotBugs to analyze java code using bugs files exclusion but that doesn't work like findBugs plugin.
I have read spotBugs documentation but unfortunately, that did not help me.
Has this feature been kept in spotBugs ?

See #18 : most of the content is hosted now at https://spotbugs.readthedocs.io/en/latest/, so the most files in this repo are obsoleted.

I'm trying to understand how the current code here maps to the state I see at http://spotbugs.readthedocs.io/en/latest/.
I honestly have no clue.

We should provide a simple how to about fixing and uploading the docs.