commit 38e33f2a193409b67ed5acaf756d7919258e3cfa
Author: Garrett Malmquist <garrett.malmquist@gmail.com>
Date:   Fri Nov 6 16:23:24 2015 -0500

    Getting the ./pants junit runner to work with Cucumber scenarios.
    
    Cucumber Scenarios generate test Descriptions that are unusually
    formatted. Cucumber sends the Scenario description as the
    "class name", and the step description as the "method name". The
    actual test class object is null.
    
    This was causing the junit runner itself to generate NPEs and fail
    on some of our internal targets which use Cucumber.
    
    This fixes the problem by making the AntJunitXmlReportListener less
    dependent on the specifics of what's stored in the class name and
    method name fields.
    
    Testing Done:
    Added a testproject run by tests/python/pants_test/backend/jvm/tasks/test_junit_run_integration.py, currently marked as xfail.
    It fails currently, but I've confirmed locally that it will pass when we release a new junit runner and upgrade to it.
    
    CI went green here: https://travis-ci.org/gmalmquist/pants/builds/89724976
    
    Bugs closed: 2512, 2513, 2515
    
    Reviewed at https://rbcommons.com/s/twitter/r/3090/

 .../junit/impl/AntJunitXmlReportListener.java      | 75 ++++++++++++++--------
 1 file changed, 48 insertions(+), 27 deletions(-)