Changed addCollectionToClasspath() so that IOExceptions (e.g., the archive being added doesn't exist) are not fatal. This allows analysis continue even when some of the aux classpath is bogus.  The issue came up because Eclipse 3.0.1 specifies some nonexistent jar files as Class-Path entries in jar manifests.
Changed addCollectionToClasspath() so that IOExceptions (e.g.,
the archive being added doesn't exist) are not fatal.
This allows analysis continue even when some of the aux classpath
is bogus.  The issue came up because Eclipse 3.0.1 specifies
some nonexistent jar files as Class-Path entries in jar manifests.


git-svn-id: e7d6bde23f017c9ff4efd468d79d66def666766b@3064 eae3c2d3-9b19-0410-a86e-396b6ccb6ab3

sewe/spotbugs,spotbugs/spotbugs,johnscancella/spotbugs,sewe/spotbugs,sewe/spotbugs,johnscancella/spotbugs,spotbugs/spotbugs,spotbugs/spotbugs,KengoTODA/spotbugs,spotbugs/spotbugs,KengoTODA/spotbugs,johnscancella/spotbugs,johnscancella/spotbugs,sewe/spotbugs,KengoTODA/spotbugs,spotbugs/spotbugs,KengoTODA/spotbugs