Return-Path: 
 <dev-return-40118-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org>
Delivered-To: apmail-harmony-dev-archive@www.apache.org
Received: (qmail 89577 invoked from network); 18 Jan 2011 19:11:58 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 18 Jan 2011 19:11:58 -0000
Received: (qmail 31295 invoked by uid 500); 18 Jan 2011 19:11:57 -0000
Delivered-To: apmail-harmony-dev-archive@harmony.apache.org
Received: (qmail 31142 invoked by uid 500); 18 Jan 2011 19:11:56 -0000
Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@harmony.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@harmony.apache.org>
List-Post: <mailto:dev@harmony.apache.org>
List-Id: <dev.harmony.apache.org>
Reply-To: dev@harmony.apache.org
Delivered-To: mailing list dev@harmony.apache.org
Received: (qmail 31123 invoked by uid 99); 18 Jan 2011 19:11:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jan 2011 19:11:56 +0000
X-ASF-Spam-Status: No, hits=1.5 required=10.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of modsrm@gmail.com designates
 209.85.216.49 as permitted sender)
Received: from [209.85.216.49] (HELO mail-qw0-f49.google.com) (209.85.216.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jan 2011 19:11:48 +0000
Received: by qwj9 with SMTP id 9so6130044qwj.36
        for <dev@harmony.apache.org>; Tue, 18 Jan 2011 11:11:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type;
        bh=CR5leBEDqFBMEGMgEWuky06Vay2a6cMKEtlA/nJ25eE=;
        b=VXQi+31oixSBOGdFQbbFdKDifhPFnkK+U2Ipj/hKlgl5i7z+oZjs8il16SmDP90Jpx
         1oUazL0LC9r46eAROMm8oH7qDMFozfJQ3PEW6LZ+4rCFovkJxJoEGI2HcD418PLInfXB
         Bba8KRrQv/BtPnQAiDSytHdggkglUWiVgFzLI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Zmv/0V3iXYSG+X9vgoiaUs1E8vYKsElYyOe3NtlLH4bG4AYyD0o/1AoQh6Y6rHVGnP
         y8/wovF+ALkp4B5Lq8wk+ufFNT/u0sxvWkCoEqn2xu/RQYQNmVnGD3F/jeF6RUiFTluX
         fGbqNXu7wMYRvms7bdOZTMdxCNOP2l8QUh/As=
MIME-Version: 1.0
Received: by 10.229.229.83 with SMTP id jh19mr4952263qcb.234.1295377886125;
 Tue, 18 Jan 2011 11:11:26 -0800 (PST)
Received: by 10.229.76.2 with HTTP; Tue, 18 Jan 2011 11:11:26 -0800 (PST)
In-Reply-To: <AANLkTimHBpPeD-on1Xp+f7RO4L63ZO+3KaH4tEso3gts@mail.gmail.com>
References: <AANLkTikpeGyyEwFHRLhF0NGn_5vszWOD+QLFONdqUux1@mail.gmail.com>
	<AANLkTimHBpPeD-on1Xp+f7RO4L63ZO+3KaH4tEso3gts@mail.gmail.com>
Date: Tue, 18 Jan 2011 19:11:26 +0000
Message-ID: <AANLkTi=fcuLnGc5G53kJrdR3NcSXV45YqRiVfF52ufqd@mail.gmail.com>
Subject: Re: [testing] Emma code coverage
From: mods <modsrm@gmail.com>
To: dev@harmony.apache.org
Content-Type: multipart/alternative; boundary=00163630fa2bc09faf049a23aada
X-Virus-Checked: Checked by ClamAV on apache.org

--00163630fa2bc09faf049a23aada
Content-Type: text/plain; charset=ISO-8859-1

On 18 January 2011 14:43, regis xu <xu.regis@gmail.com> wrote:

> On Tue, Jan 18, 2011 at 4:54 AM, mods <modsrm@gmail.com> wrote:
>
> Which JIRA did you see? Wiki page [1] may be helpful.
>
> [1] http://wiki.apache.org/harmony/coverageEMMA
>
>
Hi Regis,

thanks for the answer.

The JIRA ticket i was talking about is
HARMONY-564<https://issues.apache.org/jira/browse/HARMONY-564>.
I believe is a Harmony 5 related ticket, i thought it might have worked for
Harmony 6 too. The setup process gets confusing when it comes to run the
unit tests to generate the coverage files. It uses <junit> ant task, where
my build.xml files use <run-hdk-test>. I tried to mess around but nothing
worked for me.

I saw that wiki page and i read it before posting the topic to the devlist.
It explains what the problem is, and gives some links to a modified version
of EMMA and other config files to run it. Unfortunately the links are not
working for me, even after i log-in.

Thanks for your help,

let me know if you have any other advice please.

Roberto

--00163630fa2bc09faf049a23aada--