db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Lecavelier (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-577) Test harness should not change the user.dir property , it is meant for infomative purpose only.
Date Tue, 20 Sep 2005 09:37:28 GMT
    [ http://issues.apache.org/jira/browse/DERBY-577?page=comments#action_12329982 ] 

Thomas Lecavelier commented on DERBY-577:

Hi Suresh,

I follow the references about userDirName, it appears it's build from System.getProperties()
and I see nowhere "userDirName" is modified. If you see an occurence, could you specify where,

Anyway, it seems user.dir is only use to create a tree of nested directories in order to perform
tests. Maybe it could be remove safely from the jvm argLine used for the tests.

> Test  harness should not change the user.dir property , it is meant for infomative purpose
> ------------------------------------------------------------------------------------------------
>          Key: DERBY-577
>          URL: http://issues.apache.org/jira/browse/DERBY-577
>      Project: Derby
>         Type: Improvement
>   Components: Test
>     Reporter: Suresh Thalamati
>     Priority: Minor

> If  the  user.dir property is changed ,  you wil  find IO calls are working on different
directory than what is returned  by 
> File.getAbsolutePath()   if the file handle is created with a relative path  because
of JVM issue: 4117557 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4117557
> I think  it  is  not good  idea for test harness to change  the user.dir property.  
 It makes hard to debug tests ,  because 
> files  are not created  at  diferent location than  what is returned by getAbsolutePath().
   Atleast,   I had  fun time figuring out this :-)
> user.dir  is being  changed at the following code segment :
> org.apache.derbyTesting.functionTests.harness. RunTest.java 
>  testJvmProps.addElement("user.dir="+userDirName);

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message