Commenting out unused code.

The PhantomReporter never fires a writeFile event so I don't think this code could ever be triggered?
Built a JUnitDataReporter which outputs the data while is required to create a junit xml file.

It's easier to test in a browser so wrote the logic here first - will now copy across to the PhantomReporter for reuse by the plugin...
Added the relevant code from the JUnitDataReporter into the PhantomReporter for use from within the Phantom environment
Generating an XML file from a template based on the run specs...
Test duration in JUnit is reported in seconds rather than miliseconds...
Fixed a typo which prevented failure messages from appearing in output
Outputting additional information into the JUnit XML
Since it is available and seems to be desired by the JUnit spec [ http://stackoverflow.com/questions/4922867/junit-xml-format-specification-that-hudson-supports ]
Writing the suites out to separate xml files with the option to consolidate into one file per top level suite...
Fixing lint errors
Not dying when there is a suite with no specs - this seems to happen in the bundled requirejs example.
Added some basic documentation for the new JUnit options
Naming the generated JUnit files TEST-[name].xml as they were in the old version of the plugin for easier migration where Jenkins is searching for files named in that way.
Fix for the classname not appearing in the generated XML file...
Merge branch 'issue/11' of https://github.com/vitch/grunt-contrib-jasmine