Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

I simply launch the code, after having it instrumented and changing the JVM
parameters to add cobertura.jar and its other librairies (jakarta oro,
etc...).

After shutdown I get back cobertura.ser and source code and generate the
html report using cobertura scripts.

On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...> wrote:

>
>
> How are you starting the testing process if you are not using <junit>?
>
>
>
>
> No I am not using ant's junit.
>
> I was using the last version from the trunk, but I have now backup to the
> 1.9.4.1 version that I have recompiled and put the traces on.
>
> Fabien
>
> On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> That sounds right.   Are you using Ant’s <junit>?
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 3:24 AM
> *To:* cobertura-devel
> *Subject:* [Cobertura-devel] cobertura.ser still created in current dir
> even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Hi,
>
> During instrumentation and execution I add the java option
> -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
> create and update the cobertura.ser file.
>
> It seems that the option is well understood during the instrumentation, a
> cobertura.ser file is rightly created in the indicated file fullpath.
>
> BUT when the instrumented code is executed with the same option passed to
> the JVM another cobertura.ser file is re-created in the current working dir.
>
> Is it the right option to use ?
>
> Thanks a lot for your help !
>
> Fabien
>
>
>