To help in development, I used Aaron's Zip Project Data analysis, a new admin analysis that allows you to get a zip file containing the raw data from all the developers on a given project. After unzipping the data into my user's directory and starting up the system, I found that the design of the ProjectManager was preventing us from using Zip Project Data effectively. Basically, the ProjectManager would bomb out for an entire user if any of the project definitions for a given user had errors in them. This will occur quite frequently when using ZPD analysis, because, for example, the downloaded data will include project definitions in the user's project.doc.xml file that refer to users that aren't present in the downloaded data.
So, I made a simple change to the ProjectManager such that it only raises an error for the specific project it is trying to define, and then goes on to try to define the next project in the normal fashion for the user. This means that when you use Aaron's ZPD analysis, you'll (typically) get a bunch of errors to the console indicating that lots of the projects for the downloaded users could not be defined, but you will get the specific project you were interested in being loaded and defined successfully.
Cheers, Philip
p.s. I fixed and committed the 'line too long' checkstyle error in hackyTelemetry.
