Hi I don't know what's causing the problems you're seeing, but perhaps >>> "ant buildjarsclean" would work better for you than "ant buildjars"? >>> That build target deletes the jar files before recreating them, so you >>> wouldn't have to delete them manually. >>> >> Thanks Knut, but it doesn't work too. I still get this error:
BUILD FAILED F:\eclipsework\trunk\build.xml:1874: Unable to delete file F:\eclipsework\trunk\ jars\sane\derby.jar I often build on Windows Vista SP2 with Cygwin, and I haven't seen this > issue. My user also has admininstrator rights. Thanks Dag for sharing this. I think then the problem might with the way windows user privileges. Though I have't tried it over Windows XP to be sure if this is with other version of windows or specific to Windows 7 > think that it has something to do with having your source tree jars > in your CLASSPATH when you perform the build. Since they are in your > CLASSPATH, they are automatically opened by Ant during the build, and > hence are in use and cannot be deleted. @Bryan, Kathey thanks for bringing this perspective. May be I am not very much aware of the difference between the removal of currently used file on linux and windows platforms. If linux allows removing the files being used or if ant behaves differently(not sure if it does), then it seems to be a probable reason. It is important to keep the results for analysis after a run. For some > testing, like upgrade testing at releases it is actually important for the > old database to be still there. You could add an option though that cleans > up the test related directories before running the tests. I would have it > target very specific directories as you wouldn't want to accidentally remove > something unintended by running in the wrong directory. Kathey, thanks. Now I get it. May be this could be taken as a part of GSoC ? I am not completely aware of the intricacies behind it at the moment. Any suggestions or advises ? -- Regards Siddharth Srivastava
