<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 10, 2015 at 11:37 AM, Nils Gladitz <span dir="ltr"><<a href="mailto:nilsgladitz@gmail.com" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=nilsgladitz@gmail.com&cc=&bcc=&su=&body=','_blank');return false;">nilsgladitz@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_extra">The .json files should contain the
            package of the class.  This is what CDash uses to report the
            coverage, as opposed to the per-directory view that it uses
            for gcov.</div>
        </div>
      </div>
    </blockquote>
    <br></span>
    Doesn't that break though if there are two classes with the same
    name in two distinct packages?</blockquote></div><br><br></div><div class="gmail_extra">After looking more closely I think you're right.  We should probably incorporate the package name into $path for each file:</div><div><br></div><div class="gmail_extra"><a href="https://github.com/Kitware/CDash/blob/master/xml_handlers/JavaJSONTar_handler.php#L164-L167">https://github.com/Kitware/CDash/blob/master/xml_handlers/JavaJSONTar_handler.php#L164-L167</a></div></div>