Findbugs is great software, and my team uses it while working on our Android project. Everything is beautiful and brilliant in Eclipse, however now we are trying to automate our builds with ant and automatically generate Findbugs results for each build.
It doesn't seem so complicated. I followed this guide:
https://wiki.jenkins-ci.org/display/JENKINS/Building+an+Android+app+and+test+project#BuildinganAndroidappandtestproject-FindBugs
One of the minor issues is that I had to change ${android.jar} to ${project.target.android.jar} .
The worst part is the warnings. The following classes needed for analysis were missing: for classes that are part of the library projects we use. Some of them are our own, and we would also like to scan them using Findbugs. To complicate the situation, one of these libraries uses another lib (also our own and requires scanning), so it looks like this: Project A --uses--> Library B --uses--> Library C
Here I thought that since the Android SDK can handle all these dependencies (the C library compiled when I issue ant debug for Project A), I can somehow use it, get a list of libraries that my project depends on, and provide this findbugs task. Unfortunately, I did not.
Now I decided to manually enter all the libs, some in the class property of the findbugs task, some in the auxClasspath , which has growth potential, that I can only analyze the libraries on which the project depends. Nevertheless, I hope that what I originally tried to do is possible. Can someone show me how to extract path element
source share