Community
Participate
Working Groups
Build ID: I20070621-1340 Steps To Reproduce: 1. Open up eclipse on my box 2. Read the bogus build errors for my project related to the classpath 3. Try to modify the build path and get a bogus write error, then manually play around with the file yourself with a text editor. 4. Have Eclipse refresh the project and then stare in frustration as the error message is still there and Eclipse still can't write to the .classpath file. 5. Restart Eclipse and stare in bewildered amazement as the error is still there. 6. Use an alternative build tool to confirm that everything is fine. 7. Report an error to this bug list with these steps, because the exact cause of the bug or the steps needed to reproduce it is not known. More information: I do not know the steps to take to replicate this error. All I know is I opened up eclipse, I got a bogus build error saying a jar can't be found, and when I try to mess around with the build path I get "access denied" write errors. I know this is bogus because I can open up the .classpath file and modify it manually. I also know my project builds fine because I can build it with another build tool.
Thank you for the bug report but I do not see how this is related to Eclipse Ant integration?
sounds like a classpath issue, sending over to JDT for comment....
Please see http://www.chiark.greenend.org.uk/%7Esgtatham/bugs.html and https://bugs.eclipse.org/bugs/page.cgi?id=bug-writing.html "Access denied" errors means that you have a problem with your file system (do you have the rights to the directory containing the .classpath file?)
Please reopen if you have more information. Verified for 34M5 using I20080204-0010 build.