Integrated optional junit xml output

[edspencer]

Addresses #87, follows the 7 steps laid out in that ticket.

Adds 3 new configurations to CLI and guard config:

• junit - set to true to save output to xml files (false by default)
• junit_consolidate - rolls nested describes up into their parent describe blocks (true by default)
• junit_save_path - optional path to save the xml files to

Uses the junit reporter created by larrymyers from http://github.com/larrymyers/jasmine-reporters

Sample usage:

guard :jasmine, :junit => true, :junit_save_path => 'reports' do
  watch(%r{^spec/javascripts/.+$}) { 'spec/javascripts' }
  watch(%r{^spec/javascripts/fixtures/.+$}) { 'spec/javascripts' }
  watch(%r{^app/assets/javascripts/(.+?)\.(js\.coffee|js|coffee)(?:\.\w+)*$}) { 'spec/javascripts' }
end

We needed to do this to get Jasmine results properly integrated in our Jenkins CI server, which is now working like a charm :)

[netzpirat]

That looks perfect, thanks a lot! I'll merge and release a new version when I'm back from holiday in the first week of August, because I don't have my computer with me.

[farias-r7]

Awesome! Pretty much exactly what we needed.