Community
Participate
Working Groups
OK, I did a build after a lot of editing, and I got error messages that claimed that symbols were not resolvable. When I clicked on the error message, it gave me my new file with the error corrected. So I decided that something was confused, and I did a "Clean". I got the project could not be built due to "Problems encountered while deleting files". It did not state what the problems were. It then instructed me to "Fix the problem". Duh. If I knew what the problem was, I could fix it. The fact that it exists and has blocked me for two days and tried everything I could think of to fix it suggests that there is a more subtle problem here. The source files are kept on OneDrive, and there are three packages: the default package, called "application" and "structures". I decided that the easiest thing to do was to delete all the files, reinstall them from the repository, and do a clean and rebuild. I discovered that the "applications" directory is somehow locked against me. I tried to look at it, and it told me "access denied". Then it told me I needed permission from the "admin" account to delete it. That is the account I was logged into. However, I run with UAC enabled, so I don't normally have access. I ran Windows Explorer with admin privileges, and I could not access the directory, but discovered it had "read-only" access. When I tried to convert it to read/write, I got another error message telling me access was denied. I tried to create a new project, and have been defeated in that. Why do I have this bizarre problem, why do I get an uninformative error message, and why can't I fix it?
You might want to attached the .log file from your workspace/.metadata so we have a chance to see which part of the tool failed. OTOH, managing permissions on external file systems sounds like a task outside the scope of an IDE. Mentioning problems deleting files should already give a fair hint at permission problems at the file system level.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
