db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Ostgaard <Vemund.Ostga...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-2109) System privileges
Date Tue, 04 Mar 2008 11:47:35 GMT
Myrna van Lunteren wrote:
> On 3/3/08, Daniel John Debrunner <djd@apache.org> wrote:
>   
>> Daniel John Debrunner wrote:
>>
>>     
>>> Around line 401 of jvm.java there is code that sets the
>>> other properties that are used by the harness,
>>>       
>> I meant "used by the policy file"
>>
>> Dan.
>>
>>     
> Yes, thx, I was thinking the same thing. I got better results when I
> added -Demma.active="" to my -Djvmflags. My -Djvmflags now show:
>  -Djvmflags=-Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource^-Demma.active=
>
> We'll see how that goes...
>   
The idea with the emma.active property was that setting it (to "") would 
enable extra permissions in the policy files that were needed when 
measuring code coverage. If the emma.active property is not set, these 
permissions should be ignored by the security manager, to avoid them 
affecting the regular testing by accident. These permissions should only 
be needed if you are running with classes or jar files that have been 
instrumented with EMMA. If you are just running regular testing without 
EMMA-instrumented code, they should not be needed.

When running the junit tests the emma.active property is automatically 
set by the SercurityManagerSetup if it finds a specific EMMA-class on 
the classpath, so that the junit tests can be run with classes and jars 
that are instrumented with EMMA. Something similar (as Dan suggests) 
could be done with the old harness to make it easier to measure code 
coverage for those tests.

If the changes for DERBY-3445 affects the old harness tests, then it was 
unintentional and probably a bug.

Vemund

Mime
View raw message