It looks like you want the -auxclasspath flag to findbugs. See http://findbugs.sourceforge.net/manual/ch11.html
(I haven't actually tried this myself) Martin On Tue, May 13, 2008 at 4:37 PM, Kelly O'Hair <[EMAIL PROTECTED]> wrote: > > I'm currently looking at how we could possible include a run of findbugs > in the build process, but my conclusion right now is that we cannot do it > by default, it takes way to long to run findbugs over everything. (>12hrs). > > But I could add some minor support to the Makefiles to allow someone to > run findbugs on specific classes/packages, using a command line like this: > > findbugs -textui -maxHeap 1024 -javahome /YOUR/jdk1.6.0 -sortByClass \ > -onlyAnalyze "IMPORT_SPEC" -html -output report.html \ > CLASSES_DIRECTORY_OR_JAR > > For example, after I have built the jdk, you could run findbugs over just > the java.lang.* classes: > > findbugs -textui -maxHeap 1024 -javahome /opt/java/jdk1.6.0 -sortByClass \ > -onlyAnalyze "java.lang.*" -html -output report.html \ > build/solaris-i586/classes > > Ideally you want a fully populated classes directory or jar file so > that it can analyze all the classes properly. > (Note: using java.lang.* does not include the classes in the nested > packages).