I'm using Zend Studio to work on several PHP projects. Most of these projects include several external libraries. I've got these tucked away in a "libraries" directory within each project (using a public, application, libraries structure). The libraries are included using svn:externals - we made this choice so that it's easy to keep them up to date in a new branch, and the libraries will be included with a checkout so all unit tests can do their thing without any unexpected external dependencies.
My problem is that some of these libraries do some fairly funky stuff, and contain coding constructs that Zend Studio finds offensive. Things like invalid escape sequences in double-quotes strings, or dependencies on undefined functions (of course, after checking whether or not that function exists).
While in most cases I completely agree with Zend that it's in fact an error, these are things I cannot easily solve. While I'm all for open source, I don't feel like resolving a thousand or more escaping issues in Zend Framework. This is a problem, however, because the Errors view now has over 2.500 "warnings". About 12 of which are for my own code. They get completely swamped by the problems in the libraries, which greatly reduces the value of doing the analysis in the first place.
Is there a way to tell Zend Studio to ignore these libraries? Or is there something else I'm missing here?