[ http://issues.apache.org/jira/browse/DERBY-577?page=all ]
Myrna van Lunteren resolved DERBY-577:
--------------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Suresh indicated on the list that it
"[...] is not necessary to port this fix into 10.1 branch."
> Test harness should not change the user.dir property , it is meant for
> infomative purpose only.
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-577
> URL: http://issues.apache.org/jira/browse/DERBY-577
> Project: Derby
> Type: Improvement
> Components: Test
> Versions: 10.2.0.0
> Reporter: Suresh Thalamati
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-577_102_20060509.diff, DERBY-577_102_20060509.stat
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
